Before you digitise, you should know what has to get better.
A new CRM. A portal. Automation. AI. Software of your own.
The more important question often comes too late: which problem is this supposed to make disappear?
With Lens · takes about 3 minutes
Cause, not symptom
Not every visible friction is a technical problem.
Options, not a foregone conclusion
Remove, simplify, standard software, integration and build become comparable.
A decision, not a report
Analysis ends with a concrete next step.
When a digital decision is still unclear
Typical situations
In an unclear situation, more delivery is not automatically progress.
How solid is your next digital decision?
Problem suspected
There is friction or dissatisfaction, but symptoms and causes are still mixed. The solution is discussed quickly, while the actual question is still open.
- Still vague
- Many assumptions
- Little evidence
With Lens · takes about 3 minutes
Understand → find the cause → judge the effect → compare options → decide.
The result of good analysis is not the largest possible scope. It is a better decision.
How O/S analyses
Starting point
How does the relevant process, system or digital service actually work today?
Cause
Which problems are technical, which are in the process, and which come from roles or rules?
Options
What can be removed, simplified, configured, connected, automated or built as custom software?
Priority
Which change creates the largest sensible lever, and what can deliberately wait?
Der Ablauf zuerst
Analysis is not a prelude to a sale. It is allowed to lead to less technology.
The best recommendation can be to build nothing new.
What changes withgood analysis
Cause
The problem comes before the solution.
Symptoms are separated from causes, so action starts at the right bottleneck, not at the most visible symptom.
Options
Paths become comparable, instead of predetermined.
Several realistic paths are weighed against benefit, effort and risk before anything is fixed.
Priority
Not every weakness becomes a project.
Many observations become a sequence you can stand behind. Not every observation automatically becomes an initiative.
Decision
Analysis ends in a next step.
The result leads to a reasoned decision: deliver, shrink, postpone, or stop on purpose.
Calculate the cost of an open digital decision
- How many hours per person per week go into coordination, research and repeated decision rounds?
- How many people are regularly involved?
- How many weeks does the relevant decision stay open?
4Hours per person per week
3People involved
8Weeks until a decision
- ≈ 12 workdaysat 8 hours per workday
- ≈ 2.4 work weeksat 5 workdays per week
96 team hours until decision · 12 workdays until decision
This unsettled digital decision already ties up
3,648.00 €
The calculator quantifies internal coordination effort. Opportunity cost, lost revenue and avoided bad investments are not calculated as a flat figure.
Which open question is stopping you from deciding with confidence today?
Lens helps you focus the actual decision, and the next clarification that would help.
Common questions
- Do we have to deliver with O/S afterwards?
- Can O/S analyse systems we already have?
- Is an audit only useful when something is wrong?
- Can the result be that we do not need new software?
- Is DISCOVERY always required before FLOW, START or PORTAL?
- How is O/S different from a classic strategy consultancy?
No. The analysis is a piece of work in its own right. It should make a decision you can stand behind possible.
CONTACT
What should you analyse first?
Describe the decision you cannot yet make with confidence, or the process where you suspect unnecessary effort. You get a first reading of which question should be clarified first.