Constrange

Home/What we do/Judgement

The actual situation

Context, Judgement & Structured Problem Solving

A generic model can supply information. It cannot hold your systems, constraints, or the cost of a wrong turn.

ONE POSITIONGENERIC ANSWERCONTEXTCONSTRAINTMANY PLAUSIBLE ANSWERSONE, WITH REASONS
Fig. 07A position inside real constraintContextJudgementStructure

Overview

Clients are not paying Constrange to ask a model on their behalf. Information is cheap. What is scarce is context, judgement, and the ability to hold a specific organisation’s constraints while a path is designed.

A generic model does not know your systems, your unofficial processes, your team’s capacity, or the cost of a wrong turn. We work with the actual situation until a practical next action is clear.

Approach

Four stages before a path is treated as settled.

Each stage leaves an artefact you can challenge. Nothing is carried forward on confidence alone.

  1. 01

    Understand

    Study the work, the systems, the people, and the constraints as they are.

  2. 02

    Define

    Name the actual problem. Write the non-goals.

  3. 03

    Explore

    Hold more than one credible path long enough to compare them.

  4. 04

    Structure

    Turn the choice into architecture, owners, and sequence.

What this involves

Inside judgement.

01

Organisational context

The existing landscape, not a generic industry template.

02

Working constraints

Limits treated as design material, not as inconvenience.

03

Team capability

Recommendations that a real team can carry.

04

Priority under uncertainty

Choose when information is incomplete.

05

Solution design

Shape an answer that survives contact with operations.

06

Independent view

A position that is not a vendor's default stack.

What we hold in view

The terms of the work.

ContextThis organisation, not a sector template
JudgementA position, with reasons
StructureDecisions written down
IndependenceNot a vendor’s default stack
UncertaintyNamed rather than hidden
ActionRequired. Insight without a move is unfinished
ONE POSITIONGENERIC ANSWERCONTEXTCONSTRAINTMANY PLAUSIBLE ANSWERSONE, WITH REASONS
Fig. 07A position inside real constraintContextJudgementStructure
Artefact

A working note.

The kind of thing this work produces — inspectable, arguable, and short enough to be read.

heldJudgement
INFORMATION
Many tools could “do AI”.

CONTEXT
Incomplete records.
Tired team.
Core system frozen this year.

JUDGEMENT
Do not add a model on missing data.
Do not ask the team for a parallel process.

PATH
Stabilise the record.
Then reopen the question.

When this usually appears

  • Too many plausible answers
  • AI used as a substitute for thinking
  • A decision that needs an outside mind
  • A situation that does not fit a playbook
Questions

Judgement, asked directly.

Frequently asked questions

Is this just facilitation?

No. We take a view. The work is to make that view inspectable.

Can we use Constrange alongside an existing consultancy?

Yes. We can be the structured reading that keeps a larger programme honest.

Talk about judgement

Bring the situation as it is.

You do not need a polished brief to start. A conversation is usually enough to name the problem and decide whether there is work here at all.