Attract
Organisations discover Elliott Digital and identify potential digital problems.
How We Work
Understand the work before building the technology.
Elliott Digital starts by understanding the organisation, the people using the service, the problem, the existing process, what already works and where friction is — before deciding what technology is appropriate.
Understanding first. Technology second.
The wider picture
Where Elliott Digital’s tools fit across the journey
Attract → Understand → Sell → Deliver → Operate is the wider business and client journey. It is not the delivery method shown below — that method runs inside the Deliver stage.
Understand
An enquiry becomes a structured understanding of the organisation, the problem and the constraints. Understanding first. Technology second.
- Client Discovery Questionnaire
- Human discovery & review
- Requirements
Sell
What has been discovered is translated into understandable services, products or project options.
- Elliott Digital Catalogue
- Scope
- Proposal & agreement
Deliver
Delivery runs from agreed scope through implementation to client sign-off. The Elliott Digital method — Understand, Design, Build, Test, Learn, Improve — runs inside this stage.
- ED-OPS
- Build workflow
- Client review
- Approval
- Launch & handover
Operate
Systems are kept supported, reviewed and improved after delivery.
- Support
- Security & Operational Assurance
- Monitoring
- Improvement
- Website Opportunity Scanner is both an owned product and an Attract-stage tool.
- ED-OPS is the internal delivery operating system; Security & Operational Assurance supports the Operate stage.
- Organisation Service Hub is a developing platform for clients whose service information needs to stay accurate across channels.
- Recovery World is an active Elliott Digital project — an output of this journey rather than a stage in it.
The method
From a real problem to the right technology
The same shape of work every time. It starts with understanding and returns to it.
- UnderstandWe investigate the problem before prescribing technology.
- DesignWe turn what we learn into an appropriate service, user experience and technical approach.
- BuildWe engineer the solution with accessibility, privacy and security considered from the beginning.
- TestWe test both whether the technology works and whether it actually helps people use the service.
- LearnReal-world use shows us what assumptions were right, what was missing and what needs to change.
- ImproveWe use that learning to make the product or service better.
Step one · Understand
Nothing is designed until the work is understood
What we need to understand first
Understanding, before technology
Before recommending or building anything, we work to understand what the organisation is trying to achieve, who uses the service, what happens today, what causes friction, what information is needed, who is responsible for what, and what systems already exist.
- What the organisation is trying to achieve, and who the service is for
- What happens today, and where the friction is
- What information is needed, and who is responsible for it
This is the step most technology projects skip. It is the one that matters most.
Illustrative — every engagement is different.
Design
The system is built around the work
We do not add technology on top of a process that does not work. The work comes first; technology is chosen to fit it — not the other way round.
- PeopleWho the service is for and who runs it
- ServiceWhat the service is meant to do
- WorkflowHow the work actually happens
- InformationWhat is needed and who is responsible
- TechnologyChosen last, to fit the work
People, service, workflow and information come first. Technology comes last.
Build
The understood workflow becomes an appropriate system
Technology is selected because it fits the problem — not because it is on a list of everything Elliott Digital can do.
A principle at every layer
People keep the decisions that matter
Human review and control
Automation removes work, not judgement
Automation should not remove important human judgement. Approval points stay where decisions matter, systems are built to make responsibility clearer, and people should always be able to understand what a system is doing.
- Approval points remain where decisions have consequences
- Systems make it clearer who is responsible for what
- People can see and override what automation is doing
This is a design principle across every project, not only the AI work.
Illustrative — the human step is deliberate, not an afterthought.
Operate & improve
Launch is not the end of the work
A system is monitored, maintained and kept visible after launch. Real use shows what to improve next.
- Build
- Use
- Learn
- Improve
Build, use, learn, improve — a loop, rather than build, launch and disappear.
The connected picture
How the parts fit together
Layers of work, not an architecture diagram. Individual projects use only the layers that are appropriate to the problem.
People & organisation
Who the service is for, who runs it, and what they are trying to achieve.
- The organisation
- The people using the service
- Responsibilities
- Goals
Service & workflow
How the service works today, the steps people move through, and how it should work.
- Enquiry & contact points
- Communications
- The steps in the process
- Hand-offs between people
Information & decisions
The information the service needs, who is responsible for it, and the decisions people make.
- Structured information
- Reporting & dashboards
- Meaningful KPIs
- Decision points
Digital systems
The systems built around that work — chosen because they fit the problem, not because they are on a list.
- Websites & digital platforms
- An operational source of truth
- Automation & orchestration
- Integrations with the services a project connects to
Operations & improvement
Keeping the system running, visible and improving after launch.
- Monitoring
- Maintenance & updates
- Security visibility
- Learning from real use
Principles
What guides the systems we build
Connected, not merged
Each system has a clear role and responsibility rather than one system trying to do everything.
A clear operational home
Core relationship and delivery information lives in one operational source of truth.
Human review before it matters
Automation can surface and prepare information, but people keep control of communication and important decisions.
Automate routine work, not judgement
Use technology to reduce repetitive work while preserving judgement and accountability.
Secure, reliable and auditable
Appropriate access, logging, monitoring, privacy and operational controls are designed in.
Built to scale and evolve
Systems should be maintainable and able to change as organisations and services develop.
Talk through what you’re trying to solve
You do not need a technical brief. Tell us about the organisation, the service and where it is not working — we’ll start there.
Talk through a project