Topic Area 2 of 6
Working Method and Consulting
How I approach tasks — and why communication matters just as much as the technical solution.
Chapter 04
My Working Method
Understand
I build a complete picture of the starting situation before making assumptions.
Analyze
I break the problem down into its causes, dependencies, and constraints.
Evaluate
I weigh options against each other by risk, effort, and impact.
Decide
I make a well-founded decision and stand behind it.
Implement
I implement the solution in a structured way, with an eye on ongoing operations.
Document
I record what was done and why, so it stays traceable.
Chapter 05
Analysis and Troubleshooting
Before I intervene in a system, I want to understand what's actually happening — not just what was reported.
- I separate symptoms from causes instead of patching the surface.
- I make dependencies visible before making any change.
- I check assumptions instead of accepting them unquestioned.
- I assess risks before intervening in a live system.
- I don't start destructively — every step stays as reversible as possible.
- I think through escalation paths and recovery from the very start.
Chapter 06
Consulting and Communication
Professional expertise only works once it's understood. That's why communication isn't an add-on to consulting for me — it's the core of it.
- I meet clients where their actual level of knowledge is.
- I translate complex technical matters into understandable language.
- I explain decisions so they're traceable, not just announced.
- I name risks openly, even when it's uncomfortable.
- I document results so they remain understandable later too.