How I work
Understand.
Then get to work.
My approach to IT projects: understand the environment first, then plan changes, implement them, and verify that they work in day-to-day operations.
Working together
A question becomes
a work plan.
Our collaboration can start with a single problem. I take on a specific task with an agreed outcome. These four steps show how I approach it.
Step 1 of 4
When it grows into more.
Sometimes the initial assessment reveals a need for help in other areas too. We then establish the technical setup and agree on a gradual handoff. Ongoing support can follow if it is needed.
We agree on scope, tasks and responsibilities for each step.
01 · First, take a closer look.
I ask you to show me where things get stuck. A specific process often says more than a long requirements list. I look at the systems, data and people involved and gather existing documents and logs.
When there is an error, I try to trace the process and narrow down its cause. What needs to change? What must keep running? What do we still not know? We clarify these questions together.
The task, its boundaries and the points I need to check first.
02 · Define the way forward.
I compare the options. What will the change achieve? How extensive is the intervention? Which dependencies must we consider?
We decide what comes first, who makes decisions and when a change can go into production. I also plan a way back.
A manageable work plan with a sequence, responsibilities and checks.
03 · Make the change.
I develop, adapt or connect systems. I test the change using specific cases, including what happens with invalid data or an outage.
I raise new findings as they emerge. If the task changes, we agree on the next step before further work continues.
A testable change and the results of the agreed checks.
04 · Check it in everyday use.
The change needs to work in the actual process. We therefore check its use, outstanding issues and operations after the transition.
I record what changed, how to use it and where to look if an error occurs. We go through these points during handoff.
A traceable setup with documentation, handoff and identified remaining issues.
Practical questions
Before our
first conversation.
A specific question is enough to start. We will work out the rest together.
What do I need to get started?
A short description of the process is enough. If there is an error, the error message and an example help. These establish what I look at first.
How do we plan changes to live systems?
We agree on a time window and the checks after the switch. Data states, dependencies and a possible rollback are clarified beforehand.
What if the previous contact person is no longer available?
I start with what exists: access, systems, services and documents. We clarify backups, permissions and outstanding tasks, and agree on the responsibility I take on. I record missing knowledge and unresolved issues.
What do I get at handoff?
The changed setup, related documentation and outstanding issues. Together, we go through how to use the solution and where to look when problems occur.