The practice of building
Stay close enough to ask better questions.
Hands-on work remains part of how I learn. An architecture sketch, a small prototype, or an unfamiliar tool can reveal assumptions that a presentation leaves untouched.
The value is not in proving that I can do every role on the team. It is in understanding enough of the work to ask useful questions and make better decisions.
Let the implementation challenge the idea.
A prototype exposes the details: what information is missing, where a workflow breaks down, which dependencies are harder than expected, and what a user needs to trust the result.
That experience changes the leadership conversation. Questions become more specific. Tradeoffs become easier to discuss. Estimates and risks can be explored with curiosity.
Stay involved without becoming the bottleneck.
Technical depth should help a team exercise its expertise. I want my involvement to clarify decisions and remove obstacles while leaving ownership with the people doing the work.
Building keeps me curious. It also reminds me that strategy eventually has to meet the details.
Continue the conversation
Connect on LinkedIn