Context
Understand what exists today, what is actually blocking progress, who the change affects and what a useful outcome would look like.
How I work
Clear context. Clear scope. Clear delivery.
The exact workflow changes with the problem, but the discipline stays the same: understand first, make the important decisions visible, implement against a real scope, then verify what shipped.
Decision
Reduce the important unknowns, choose the smallest sensible technical path and make the trade-offs visible before implementation expands.
Implementation
Build or change the agreed system directly, keeping communication tied to real progress, decisions and blockers rather than ceremony for its own sake.
Verification
Check the result against the actual problem: functional behavior, responsive use, important edge cases and the agreed acceptance boundary.
Handover
Leave the work understandable: agreed access, code or assets, important implementation notes and a clear next step if more work is justified.
Working principles
Predictable enough to trust. Flexible enough for real software.
- 01Scope changes are discussed before they silently become extra work.
- 02Evidence beats assumptions when debugging or changing an existing system.
- 03The project should stay understandable to the people who own it after delivery.
- 04A smaller correct next step is better than unnecessary complexity.
Next step
If the problem is clear enough to discuss, it is clear enough to start the conversation.
Send the current context and desired outcome. We can decide whether the right next move is a bounded implementation task or a short discovery step.