ORVANIS
Analysis Day
Know which change is worthwhile.
Duplicate work, follow-ups and stalled tasks take time. During an Analysis Day, I examine an area agreed with you. You learn which causes are supported by evidence and which change you should investigate or implement next.
Enquire about an Analysis DayOne day · one agreed scope · price on request
- Duplicate work
- Excel lists
- Email chaos
- Delays
- Constant searching
- Manual handovers
- Data quality
- Hidden dependencies
- Shadow processes
- Missing ownership
- Security risks
From the visible problem to an evidenced cause.
I examine the affected workflow, its data paths and technical dependencies, speaking with the people who actually do the work.
The Loss Indicator supports an initial self-assessment and is an optional starting point.
The Analysis Day examines the agreed area using your actual workflows and records.
Define the task
I agree the reason, the question to answer and the area to investigate with you.
Preparation
I identify the information, contacts and access needed so the investigation can begin with a clear focus.
Analysis Day
I examine the steps, data paths and dependencies and distinguish supported causes from untested assumptions.
Prepare your decision
I discuss the results with you: which change appears useful, what it requires and which questions still need answering.
Narrow down the cause
You see where work stalls or is repeated. Supported causes, ruled-out assumptions and open questions are clearly distinguished.
Weigh effort against benefit
I compare a change’s expected benefit with the work and dependencies involved. Where your data allows, I assess time gains, avoidable spending and expected implementation effort. Assumptions remain explicit.
Approve, defer or reject
You receive a reasoned recommendation for the next step and know which prerequisites are still missing. You can then decide on implementation or deliberately defer an action. I record the findings for your internal discussion.
- A workflow regularly ties up several employees.
- Data is transferred manually between applications.
- The cause of delays is unclear.
- You need a basis for the next investment decision.
- The required data transfer is already described.
- A specific fault needs investigation.
- A form or approval workflow is clearly defined.
- A project needs technical support.
SCOPE AND PRICING
One day within the agreed scope.
Preparation based on systems and available information.
Remote or on-site delivery by agreement.
For the proposal, I clarify the scope, preparation required and any necessary travel. Before commissioning the work, you know which question I will investigate and what is included. Any subsequent technical implementation is commissioned separately.
Which question should the Analysis Day answer?
Briefly describe your situation and the decision you face. I discuss whether an investigation is useful or a specific implementation assignment can already be defined.