I have been experimenting with a simple workflow framework based on four stages:
Define → Design → Develop → Deliver
The idea is straightforward. Before building a solution, spend time understanding the challenge and designing the solution. Only then proceed to implementation and delivery. This sounds obvious, but many projects jump straight into implementation.
To test the approach, I applied the same workflow to three completely different challenges:
- A spatial estimation study using geostatistical techniques.
- A hydrology workflow for extracting aquifer parameters from pumping and recovery curves.
- A short horror novel written with AI.
Three very different outcomes. Three very different domains. One workflow.
What surprised me was that it worked well for creative writing. Without a good specification it was very, very difficult to “vibe” an AI generated horror novel with more than 500 words. Sentences degraded to one word. Paragraphs degraded to one sentence. And the overall story was not very good.
The experiments reinforced something I have observed throughout my consulting career. Most project failures happen long before implementation begins. Poorly defined challenges produce poorly designed solutions. Poorly designed solutions create implementation problems. The 4D’s framework attempts to address this by separating thinking from doing.
I will be share each example, along with some observations about clarity, abstraction, product management, knowledge retention, and the role of AI in modern workflows.
The examples themselves are interesting. The lessons behind them are even more interesting.