Four phases of development: A structured approach to information projects
Last week, a former colleague shared their frustration with me: “Sven, they really could have used your process.”
They were experiencing a stalled information system project at their company, one that lacked direction, alignment, and momentum. Their comment reinforced something I’ve observed throughout my career: too many projects fail because they skip the foundational steps needed for success.
And my colleague referred to a four-step framework I utilize that ensures clarity, alignment, and collaboration from start to finish. While inspired by data modeling methodology, this process applies to virtually any solution development project.
Phase 1: Conceptual Design - Define the Vision
This phase is all about ideas, strategy, and business needs, without technical constraints. The goal is to define what success looks like before technology enters the equation.
Common Pitfalls:
DON’T get bogged down by existing systems. Familiar tools can lead to "that’s how it’s done" thinking, limiting creativity.
DON’T rush to implementation. Research consistently shows successful projects allocate more time to planning than execution (Harvard Business Review Article).
Best Practices:
DO conduct thorough business analysis to define the current state, desired future state, and possible solution paths.
DO focus on business requirements before considering technical constraints.
At this stage, the process is entirely business-driven, ensuring that technology serves the strategy—not the other way around.
Phase 2: Logical Design - Validate and Refine
Once the conceptual design is clear, we validate our assumptions using prototypes, real data, and user feedback. This step prevents misalignment before the technical build begins.
Common Pitfalls:
DON’T present a "black box" solution and expect business stakeholders to trust it blindly. Transparency in logic builds confidence and adoption.
Best Practices:
DO use accessible tools for prototyping. I often use Excel, as Finance teams can easily follow the logic and calculations.
DO collaborate with technology partners to assess technical feasibility before moving forward.
This phase ensures the business and technical teams are aligned, setting the stage for efficient execution.
Phase 3: Technical Design - Build a Scalable Foundation
With a validated logical design, the technical team now creates platform-specific schematic designs.
Common Pitfalls:
DON’T allow the business analyst to disengage. Without their oversight, the design may drift from the original business objectives.
Best Practices:
DO keep business analysts involved to ensure alignment with the original requirements.
DO prioritize clear documentation—without it, long-term sustainability suffers.
At this stage, the technical team takes the lead, but continuous business engagement prevents misalignment.
Phase 4: Implementation - Deliver and Adapt
Finally, the solution is built and deployed. However, development is just one part of a successful implementation.
Common Pitfalls:
DON’T overlook user acceptance testing (UAT). A project isn’t complete until business users validate that it meets their needs.
DON’T neglect change management. Even the best-designed systems fail if users are not properly trained and supported.
Best Practices:
DO plan for training, communication, and ongoing support to drive adoption.
DO ensure that business and technical analysts work together during deployment to confirm the system meets expectations.
A great system isn’t just about technology, it’s about people, processes, and adoption.
Why This Process Works
Too many companies are eager to start coding before defining their goals. That’s like hiring a contractor to build a mansion without architectural plans. The early phases ensure clarity and alignment, while the later phases add technical precision.
Over 20 years, I’ve led financial planning and business intelligence transformation projects for multiple companies. While I’m not a developer, I specialize in business analysis, strategy, and cross-functional collaboration, the elements critical to the early phases of an information project.
The secret to avoiding stalled projects?
Thorough planning.
Strong collaboration between business and technology.
A structured process that ensures alignment at every stage.
If you’re considering an FP&A transformation or another business intelligence initiative, I’d love to discuss how this framework can increase your project’s success.
Let’s connect for a complimentary conversation! CONTACT ME
