Project evolution phases

We must know in which state is the company before start taking decisions following the 3X model. This model doesn't only apply to only the company, but also for each for their projects / business units.

Explore

There is an idea for solving a problem / necessity on the market. The uncertainty of knowing if the idea will solve the problem is so high that we will have to explore quickly and provide rapid solutions to materialize the solution. "Don't worry, be crappy". Use NoCode, SaaS or whatever to test it fast.

Expand

We have proven that our solution solves the problem / necessity. We are starting to make marketing of it and implementing new features of the product. Now we have to focus on the expansion. The decisions that are taken must not suppose a bottleneck for the company. We can't over promise to be kind, we have to explain properly and sincerely what can be done or not. Ask why some goals are set.

Extract

Service works properly and business is predictable. We have to apply dynamics and techniques to maximize company profit reducing costs.

---

How to

Evolution doesn't have to be iterative, but incremental

Example of a Minimum Viable Project:

---

Consolidate standards

Consolidating standards in a project context means capturing, harmonizing, and embedding all agreed‑upon processes, tools, metrics, and best practices into a single, accessible framework. Rather than letting teams reinvent the wheel, you create a “source of truth” that everyone refers to—covering everything from coding conventions or documentation templates to approval workflows and quality criteria.

Continuous improvement relies on iterative cycles of planning, executing, checking, and acting. Without a stable set of baseline standards, each improvement cycle risks drifting away from prior gains or introducing inconsistency. By consolidating standards you:

• Lock In What Works: Capture lessons learned, process tweaks, and newly discovered best practices so that proven methods become part of the standard toolkit.
• Ensure Repeatability: When everyone follows the same documented approach, successes are reproducible across teams and projects.
• Measure Progress Accurately: With clear metrics and definitions in place, you can objectively compare “before” and “after” states and quantify improvement.

Design cycle

A design cycle is a structured, iterative process that guides teams from understanding a problem all the way through to delivering—and then improving—a solution. Rather than trying to “get it right” on the first pass, a design cycle breaks work into repeatable stages, each with its own goals and checks, so you continually learn, adapt, and reduce risk.

• Agility & Adaptability: Each pass through the cycle refines both the product and the process, making the team better at estimating, planning, and executing.
• Reduced Waste: Early validation and frequent testing ensure you spend less time on non‑viable features or solutions.
• Higher Quality & User Satisfaction: Continuous user input and rigorous testing lead to products that truly meet needs and perform reliably in the field.
• Transparent Progress: Clear, repeatable stages with built‑in checkpoints help stakeholders see exactly where you are—and what remains—at any time.
• Scalable Governance: Whether you’re a small startup or a large enterprise, this framework can flex to projects of any size while maintaining consistency in how work gets done.

Steps of a design cycle

Idea

• Encourages Creativity & Divergent Thinking: By explicitly carving out time to brainstorm freely, teams generate a wider range of possible solutions, some of which may be truly innovative rather than incremental.
• Early Engagement: Stakeholders (users, sponsors, cross‑functional experts) can weigh in from the very beginning, ensuring diverse perspectives shape the direction.

Validate

• Risk Reduction: Quickly screens out unworkable or unprofitable ideas before dedicating development resources.
• User‑Centered Focus: Using lightweight techniques (surveys, interviews, paper prototypes) ensures that only ideas with real user appeal advance.

Define Solution

• Clarity of Scope: Translates validated ideas into concrete requirements, wireframes, or specifications—removing ambiguity about what you’re building.
• Alignment: Gets all stakeholders on the same page around objectives, success metrics, and “must‑have” vs. “nice‑to‑have” features.

Develop

• Incremental Progress: Breaking the build into smaller, manageable increments makes scheduling, resource planning, and progress tracking more reliable.
• Early Value Delivery: Even partial prototypes or alpha releases can start generating feedback or revenue sooner.

Test

• Quality Assurance: Systematic functional and usability testing uncovers defects and UX issues before launch, reducing costly post‑release fixes.
• Data‑Driven Refinement: Insights from real users and automated tests guide targeted improvements rather than guessing at what needs work.

Deliver

• Predictable Release Cadence: By treating “delivery” as a distinct phase, teams can lock down deployments, prepare support/training materials, and manage change more smoothly.
• Market Responsiveness: A clear delivery milestone lets marketing, sales, and operations plan around a firm go‑live date.

Feedback

• Continuous Improvement Loop: Capturing user reactions, usage metrics, and internal retrospectives feeds directly into the next Idea phase—so the cycle never goes stale.
• Stakeholder Confidence: Demonstrates that you listen and adapt, which builds trust and often uncovers new revenue or efficiency opportunities.