Your systems work.
Can your customers complete the task?
An app can be available and a process technically correct, while a customer still cannot sign in, recover an account or finish an application.
Ecothesis investigates one important customer journey across the service, the person’s devices, accounts, authentication and available assistance. Find where people get stuck—and what needs to change.
Discuss a customer journeyStart with the task you want customers to complete. We agree the study scope and fixed fee before work begins.
Illustrative photograph: Serena Tyrrell / Unsplash
What happens between access and completion?
Your team may see an available service, a successful login or a closed support request. A field investigation looks at whether the person can carry the task through to a useful result.
The study is designed for digital service and customer operations leaders in banks, telcos, utilities, government and technology organisations.
- A sign-in code arrives on a device the person cannot use while completing the task.
- Account recovery relies on an old phone number or inaccessible inbox.
- A journey moves between an app, a browser, email and a support call, losing continuity.
- Instructions assume knowledge, access or assistance that is unavailable.
- An AI response appears useful, but the next action remains out of reach.
Observe. Diagnose. Retest.
Choose a customer activity that matters. Agree the people, devices, conditions and evidence needed to investigate it.
See the whole task
Observe agreed sessions across the service and the customer’s wider communication environment. Record where progress stops, workarounds appear or help becomes necessary.
Focus: completion, effort, control and recovery.
Explain the failure
Map the dependencies between devices, accounts, authentication, instructions and support. Separate observed evidence from hypotheses and rank practical corrections.
Focus: what failed, why it matters and who can act.
Check the agreed changes
Retest corrections made available within the agreed scope. Compare what customers can complete before and after, and document remaining barriers and limitations.
Focus: evidence for the next decision.
Evidence your team can act on
A bounded study with agreed deliverables and an executive discussion of the findings.
Participant numbers, test conditions, timing, access requirements and retest arrangements are defined in the proposal.
- Journey and failure-point map: the steps, dependencies and barriers observed.
- Supporting evidence: deidentified observations, with consent and agreed handling arrangements.
- Ranked corrections: practical actions, responsible teams and unresolved questions.
- Retest findings: before-and-after observations where changes were available, including what remains unverified.
- Executive report and presentation: findings, operational implications, limitations and recommended next decisions.
Follow the task into everyday use
I’m Allen Wade. I bring more than 20 years of ICT experience and an MBA in Finance to investigating communication environments.
My field work includes shared calendars, mobile access, account recovery, connected controls and everyday communication. That experience informs a practical question: can this person complete the action in the environment they actually have?
My books develop this thinking, including The Last Metre of AI.
A clear scope from the start
This is a fixed-fee customer journey investigation. Software development, system changes and wider rollout are separately scoped.
The study does not provide penetration testing, infrastructure performance testing, regulatory certification or a comprehensive accessibility compliance audit.
Ecothesis does not provide ad-hoc PC repair, printer troubleshooting or hourly tech support.
Testing uses authorised environments, agreed access and consenting participants. Test accounts or sandbox environments are used where appropriate. Evidence handling, credential boundaries and reporting permissions are agreed before fieldwork.
AI readiness and integration
If the study identifies a useful role for AI or assisted workflows, a separately scoped trial can test the proposed approach.
Define the intended action, the permissions it requires, how a person stays in control and what happens when the system fails. Then test whether the approach helps complete the task.
Any implementation or follow-on trial has its own deliverables, fixed fee and approval. It is not assumed as part of the study.
The thinking behind the work
These books draw on practical field experience in communication environments, connected systems and AI. They explore the thinking that informs this work.

Ecothesis
Why working devices can still leave everyday tasks out of reach—and how the whole communication environment shapes the outcome.
View Ecothesis on Amazon
Orchestrated Communications for Independence
A practical guide to simpler communication environments, connected homes and responsible AI, built around what people want to do.
View Orchestrated Communications on Amazon
The Last Metre of AI
Exploring the gap between what AI can do and the useful, completed outcomes people actually receive.
View The Last Metre of AI on AmazonWhich customer journey needs a closer look?
Tell me the task, where customers appear to get stuck and what your organisation needs to understand. No detailed brief is required for the initial conversation.
Discuss a customer journeyOr call 0411 180 777.
A conversation to explore fit, followed by a written scope and fixed-fee proposal.