Structured interviews
Interviews are used because they expose the workarounds, ownership gaps, informal controls and decision bottlenecks that rarely appear in a survey or system report.
ITZAMNA diagnostic workspace
The structured method behind Telstar’s diagnostic work.
ITZAMNA gives advisory work a repeatable backbone: capture evidence, compare perspectives, apply defined scoring, link findings to sources and sequence the next moves. It helps ensure recommendations are grounded in what the business actually shows, not workshop opinion, vendor preference or generic best practice.
Evidence capture
Interviews, observations and system signals are captured against a consistent diagnostic frame.
Perspective comparison
Different teams and business units can be compared to reveal agreement, tension and blind spots.
Traceable findings
Recommendations link back to what was seen, heard and assessed, not generic best practice.
Sequenced action
Findings are converted into practical next moves, with dependencies and confidence visible.
What it is
A diagnostic backbone, not another dashboard.
ITZAMNA exists to make advisory diagnosis more disciplined. It gives the work structure, evidence trails and consistency without pretending software replaces senior judgement.
Most growing businesses do not lack ambition. They lack a reliable picture of how the business actually operates across people, process, data, systems, integration, automation and control. ITZAMNA gives Telstar a structured way to build that picture before larger decisions are made.
The platform supports the diagnostic work. It helps capture input consistently, compare patterns across business areas, expose priority tensions and turn findings into a sequenced route forward. The judgement remains human. The method makes that judgement more traceable.
How the method works
From scattered evidence to a clear operating picture.
The value is created by combining structured human discovery with software-enabled consistency. Interviews expose the real story. Evidence keeps the work grounded. Scoring creates comparability. Sequencing turns insight into action.
Seven Pillars framing
Evidence is assessed across capabilities, processes, data, applications, integrations, automation and controls so one visible symptom does not dominate the diagnosis.
Defined scoring and synthesis
Scoring and assessment logic provide a consistent baseline. AI can assist with pattern recognition and initial synthesis, but it does not replace evidence, scoring or professional judgement.
Sequenced recommendations
Findings are translated into priority actions, dependencies and next steps so leaders can see what to do first, what can wait and where risk needs active control.
Lifecycle
A practical route from diagnosis to stable change.
The stages keep the work sequenced. They prevent the common pattern of selecting systems, launching automation or committing to AI before the operating model is understood.
Diagnose
Map the current operating reality before money, platforms or programmes are committed.
Architect
Shape a coherent target direction across the business, not just the technology estate.
Sequence
Prioritise the next moves in the right order so change reduces risk instead of multiplying it.
Deliver
Move from design into execution with enough clarity to avoid avoidable rework.
Stabilise
Embed the change so the business becomes easier to run, govern and improve.
Expanded stage detail
Diagnose
Diagnose is where the business stops relying on surface symptoms and starts building an evidence-backed view of what is really happening. It combines structured interviews, artefact review, operating observations and system signals to expose where friction, duplication, weak ownership and hidden manual work are creating drag.
- What this includes
- Stakeholder interviews, evidence capture, business-unit comparison, Seven Pillars assessment, confidence scoring and issue clustering.
- What it reveals
- Where the business is compensating for unclear process, fragmented data, duplicated applications, brittle integrations, premature automation or reactive controls.
- What the client gets
- A diagnostic readout that explains what is wrong, why it matters, which constraints are most material and where further design or delivery work should focus first.
Expanded stage detail
Architect
Architect translates diagnosis into a practical target shape. It connects capabilities, processes, data, applications, integrations, automation and controls so proposed change does not optimise one area while stressing another. The point is not to create abstract diagrams. It is to clarify how the organisation should operate and what technology needs to support.
- What this includes
- Target operating principles, capability alignment, data ownership, application role clarity, integration boundaries, automation posture and control design.
- What it prevents
- Tool-led change, vendor-defined operating models, duplicated capability, over-customisation, unmanaged integration debt and AI or automation built on weak foundations.
- What the client gets
- A coherent target direction that leadership can understand, delivery teams can work from and investment decisions can be tested against.
Expanded stage detail
Sequence
Sequence turns insight and target direction into an ordered route forward. It separates urgent constraints from attractive distractions, identifies dependency order and makes trade-offs visible. This is where the business avoids trying to fix everything at once or funding the most visible issue while leaving the structural cause untouched.
- What this includes
- Prioritisation, dependency mapping, confidence assessment, effort/value balance, sequencing logic, roadmap shaping and decision checkpoints.
- What it clarifies
- What should happen first, what can safely wait, what must be stabilised before automation or AI, and where further discovery is needed before commitment.
- What the client gets
- A practical improvement sequence that reduces decision noise and gives leaders a defensible basis for budget, phasing and delivery focus.
Expanded stage detail
Deliver
Deliver is where the agreed sequence becomes controlled action. The focus is keeping delivery connected to the evidence and architectural intent established earlier, so implementation does not drift back into isolated workstreams, vendor defaults or local optimisation.
- What this includes
- Delivery shaping, architectural guardrails, decision support, workstream alignment, dependency management and practical governance.
- What it protects
- The integrity of the diagnosis and design as real delivery pressures emerge, deadlines tighten and local decisions begin to accumulate.
- What the client gets
- Delivery support that helps change move forward without losing the clarity that justified the work in the first place.
Expanded stage detail
Stabilise
Stabilise ensures the change holds after the initial programme energy has passed. It reinforces ownership, measurement, controls, operating rhythm and learning loops so the business does not slide back into fragmented workarounds or unmanaged complexity.
- What this includes
- Control embedding, operating cadence, adoption review, benefits tracking, architecture hygiene, issue monitoring and continuous improvement routines.
- What it reduces
- Regression, unmanaged exceptions, post-project drift, weak governance, unclear ownership and the need for repeated corrective programmes.
- What the client gets
- A more stable operating foundation that is easier to govern, improve and build upon.
What it produces
Outputs that connect the evidence to the decision.
The aim is not to create more documentation. The aim is to give leaders a clearer view of what is wrong, why it matters and what should happen next.
Diagnostic readoutA clear view of operating friction, structural weaknesses and priority constraints.
Evidence-backed findingsIssues linked back to interviews, observations, artefacts and assessed signals.
Leadership alignment viewPerspective gaps across teams, functions or business units made visible.
Sequenced improvement planA practical route that separates immediate moves from later design and delivery work.
What structured diagnosis can show
What structured diagnosis can look like in practice.
These examples show the type of operating picture ITZAMNA is designed to support: summary health, comparative insight, evidence-backed findings and sequenced action.
Run Overview
Overall diagnostic health, confidence, priority focus, findings and next actions in one place.
Comparative Insights
A view of where business areas agree, diverge or expose hidden operating tension.
Findings Workspace
Findings connected to sources, affected pillars, recommendations and evidence trails.
Connected framework
ITZAMNA gives the work its sequence. Seven Pillars gives diagnosis its structure.
Together, they help leadership teams see what is wrong, why it matters and what should happen next before committing to larger transformation or AI investment.