WHEN THE
TECHNICAL SITUATION
GETS DIFFICULT.
Some problems are not caused by technology alone.
Different expectations, different priorities,
different interpretations of responsibility and
different technical opinions can turn a manageable
problem into a difficult one.
The Peacemaker role exists to bring the technical
reality back into the conversation.
AN INDEPENDENT
TECHNICAL VOICE.
When a project becomes difficult, technical
decisions can quickly become mixed with
commercial interests, assumptions, frustration
and personal opinions.
An independent technical perspective can separate
those things and establish what is actually
happening.
FACTS
Establish what the system actually does,
rather than what people believe it does.
CONTEXT
Understand why decisions were made before
deciding whether they were right or wrong.
OPTIONS
Make the available technical choices visible,
including their consequences.
DIRECTION
Help everyone understand what should happen
next.
KEEP THE
TECHNICAL DECISIONS
CLEAN.
Technical governance is not about adding bureaucracy.
It is about making sure that important technical
decisions are understood, documented where necessary,
challenged when appropriate and made for the right
reasons.
ARCHITECTURE
Keep architectural decisions aligned with the
actual requirements and long-term direction.
CUSTOMISATION
Challenge unnecessary customisation before it
becomes another permanent dependency.
INTEGRATION
Understand where systems meet and who is
responsible for what happens between them.
RESPONSIBILITY
Make ownership of technical decisions and
consequences clear.
FROM
PROBLEM
TO SOLUTION.
Difficult situations rarely appear at a single
point in a project.
They usually develop through a combination of
decisions, compromises, misunderstandings and
technical debt.
The objective is to understand the complete
sequence rather than simply fixing the latest
visible symptom.
DO NOT FIX
ONE PROBLEM
BY CREATING ANOTHER.
Existing NAV and Business Central systems contain
years of business knowledge, processes and investment.
Moving forward does not mean throwing everything away.
It means understanding what should be retained,
what should change and what should finally be left
behind.
EXISTING VALUE
Identify functionality that still provides real
business value.
TECHNICAL DEBT
Distinguish useful legacy behaviour from technical
debt that should no longer be carried forward.
FUTURE COST
Consider the consequences of today’s technical
decisions on tomorrow’s upgrades and support.
CONTINUITY
Protect the business processes that actually
matter while improving the technology underneath.
SOMETIMES THE
RIGHT ANSWER
IS UNCOMFORTABLE.
A Peacemaker is not there to take sides.
The responsibility is to make the technical situation
understandable and to say what needs to be said,
even when the answer is inconvenient.
That can mean challenging a customer requirement,
questioning a technical decision, exposing an
architectural weakness or explaining why something
cannot reasonably be delivered in the proposed way.
The objective is not to win an argument.
The objective is to reach the right decision.
SOLVE THE
DIFFICULT PART.
The best technical relationships are not built
around agreeing with everything.
They are built around trust, competence and the
freedom to challenge each other when something
does not make sense.
Sometimes that means development.
Sometimes consultancy.
Sometimes architecture.
And sometimes simply bringing the right people
around the same table.
LISTEN
Understand the people, requirements and
constraints before proposing a solution.
CHALLENGE
Question assumptions when the technical
evidence says they should be questioned.
CLARIFY
Remove ambiguity and make the real problem
visible.
RESOLVE
Establish a practical way forward that
everyone can understand.
HAVE A
DIFFICULT SITUATION?
If a project has become complicated, a technical
decision is being questioned, or different parties
cannot agree on the way forward, we can help make
the situation understandable.
Tell us what is happening.