| VUCA | VUCA Prime |
|---|---|
| Volatility: The brand-new feature we envisioned is a result of a change in requirements from the stakeholder community or as a result of demand for innovation. | Vision: Following discussions with stakeholders and understanding the product-market fit, we gain a vision of what the feature will look like and accordingly make a plan for its release. |
| Uncertainty: Once we have the features developed, there is uncertainty as to whether or not it is compliant with market expectations & if it is user-friendly. | Understanding: In order to deal with this problem, the feature is made available in limited quantities, and ab-tests are conducted to learn more about user behavior. |
| Complexity: Prior to coding a new feature, we need to consider the feasibility and scalability of the upcoming feature from a code and architecture perspective. This ensures that we do not overcomplicate the system. | Clarity: To get an overview of which solution is the most feasible, there are design discussions among the engineers, and RFC's/POC's are created so that everyone in the team is on the same page. |
| Ambiguity: The problem can emerge when there is insufficient communication between team members or within the organization regarding a feature release. | Agility: We follow an Agile methodology that focuses on collaboration between all members of the team and makes sure each individual has ownership over the task. Clearly defined OKRs are established so that everyone knows what to expect. |
-
-
Save shlokashah/5c4a3a294781bca59459be194b6d02fa to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment