Cognitive Laboratory / Diagnostic

Before we design the future, we make the present visible.

The ETHOS Audit is a short, intensive diagnostic. It converts interviews, observation and operating evidence into a shared model of how the enterprise works - and where connected intelligence can create meaningful leverage.

What the audit is

A decision system, not a technology shopping list.

The audit does not begin by asking which automation to install. It begins by asking what the organisation is trying to make true, why progress is difficult to see, and what evidence would justify intervention.

Its purpose is to reduce expensive guessing. It establishes a common language between leadership, teams and technical builders before commitments become architecture.

Direction

Is strategy specific enough to guide everyday choices?

Signals

Can the right people see customer, team and market movement in time?

Decisions

Are ownership, authority, thresholds and escalation paths clear?

Workflows

How does work actually move across people, tools and hand-offs?

Time

Do calendars express the organisation's real priorities and capacity?

Relationships

Can important conversations and commitments be found and continued?

Economics

Are costs, value pathways and assumptions visible by initiative or stream?

Knowledge

Does useful learning become retrievable organisational memory?

AI readiness

Where can AI safely strengthen work, and what must remain human?

Governance

Are access, consent, review, risk and accountability designed into the system?

The diagnostic path

From lived experience to an agreed operating picture.

The duration varies with availability, complexity and scope. The sequence remains stable so evidence can be compared and decisions can be explained.

Frame

Agree the questions, boundaries, decision makers and evidence needed.

Listen

Interview leadership, operators and selected stakeholders close to the work.

Observe

Trace real workflows, tools, calendars, hand-offs and exceptions.

Model

Map dependencies, friction, value pathways, readiness and assumptions.

Prioritise

Rank interventions by leverage, feasibility, risk and proof speed.

Debrief

Align the team on what is true, what matters and what happens next.

What the organisation receives

A shared basis for action.

These are working artefacts. They are designed to help the team decide, build, govern and learn - not to disappear into a presentation folder.

Enterprise field map

A shared view of the people, systems, signals and decisions shaping performance.

Friction and leakage register

Where time, context, trust, opportunity or money is being lost.

Opportunity architecture

Potential interventions connected to dependencies, value pathways and risk.

Readiness and maturity profile

A plain-language baseline across the audit lenses, with evidence behind each rating.

Activation priorities

A sequenced set of high-leverage moves, owners, success markers and governance needs.

Evidence design

What must be measured to decide whether each system is useful enough to continue.

GOOD AUDIT INPUTS

Honesty beats polish.

Access to leaders and people closest to the work
Representative workflows, calendars, tools and reports
Permission to discuss exceptions and workarounds
A decision maker willing to resolve trade-offs

Incomplete evidence is not a reason to delay. Its absence is itself a finding - as long as the organisation is willing to see it.

Five questions to ask now

What important signal reaches us too late?

Which decision repeatedly waits for one person's memory or approval?

Where does the same context get rebuilt every week?

Which activity looks busy but has no agreed proof of value?

What would the team need to run this system without us?

Discuss your operating reality ↗

Context map

The question: What happens before anything is built?

See how interviews, workflows and evidence become an activation map. Continue with the view that best matches the decision in front of you.

← BACK FOR CONTEXTMethod