05 / CUSTOMER OUTCOMES, DELIVERY AND ADOPTION
Outcome Manager
Keep the team connected to the result the customer needs.
STEP INSIDE THE WORK
AN ILLUSTRATIVE PROJECTThe feature shipped. Did the customer’s work improve?
An AI support assistant is live, but handling time and repeat contacts have barely changed. How do you move from delivery to a useful outcome?
YOUR MOVE / 01
Define the outcome and the baseline.
Carry the discovery brief into a plan for one enquiry category. Agree what resolution quality and handling time mean, where the data comes from and who accepts the result. Map delivery dependencies and adoption risks with the lead.
WHAT YOU MAKE VISIBLE
A baseline and agreed measures
A scoped plan with owners
Acceptance criteria and risks
Think from first principles.
Make your reasoning visible.
01 / YOUR MISSION
A solution is shipped. What actually changed?
A team launches an AI assistant. The demo worked, the tasks are closed, and the customer’s work is still taking too long. You want to know why. At devx, an Outcome Manager connects the customer’s goal to the work, the rollout and the evidence of impact. You will work alongside engineers and experienced delivery colleagues to keep a defined workstream moving towards a useful result. Bring analytical curiosity, clear communication and the habit of following through.
A scoped customer outcome across delivery, adoption and measurement. Graduate entry starts with a defined workstream and experienced guidance; responsibility grows with demonstrated judgment.
We reimagine customer interactions, business operations and enterprise architecture around AI. You bring fresh questions. Experienced practitioners bring context and judgment. The work connects both to a real customer outcome.
02 / WHAT YOU WILL WORK ON
Make your curiosity
useful.
Make the outcome concrete
Carry the discovery brief into an outcome plan with the customer and delivery lead. Document the baseline, agreed measures, data sources, acceptance criteria and who will make each decision. Separate features delivered from the business change they should enable.
Turn the goal into coordinated work
Help break the workstream into milestones, tasks and dependencies with engineering colleagues. Keep owners, decisions, risks and next steps clear. Surface blockers early and bring scope or timeline changes to the accountable lead.
Stay close to the users and the product
Understand how the workflow operates in practice. Reproduce reported issues, gather examples and translate feedback into clear questions or acceptance tests. Help coordinate user acceptance testing and make readiness gaps visible before rollout.
Help the change take hold
Support rollout planning, user onboarding, training and customer champions. Combine usage data with conversations to identify friction, then coordinate a practical improvement with the right colleague. Adoption matters when it helps users accomplish the intended task.
Show the evidence of value
Build simple trackers or dashboards with spreadsheets, SQL or the data team. Review agreed measures such as handling time, resolution quality or rework. Check comparable time periods and case types; a before-and-after difference alone does not prove the solution caused the improvement.
Close the loop with honesty
Prepare concise customer updates and outcome readouts: what changed, what remains uncertain, and the next action. Document decisions and reusable lessons. Ask for help early when delivery, quality or adoption puts the customer goal at risk.
What good work looks like
- An outcome plan with a clear baseline, measures, responsibilities and acceptance criteria.
- A workstream whose progress, dependencies and risks are visible to the people who need to act.
- A customer readout that connects adoption and quality to observed value, including unresolved limitations.
Use approved AI tools to synthesise meeting notes, explore data and prepare progress updates. Verify decisions with their owners and numbers against the source; keep an explicit boundary between observed facts, assumptions and suggested actions.
03 / YOUR STARTING POINT
Bring a foundation.
Build the range.
Coursework, personal projects, research and student initiatives all count. Previous full-time experience is not required.
- Structured problem-solving: turn an unclear goal into specific questions, actions and evidence.
- Comfort with spreadsheets, percentages, averages and basic data interpretation. Explain how you checked a number and what it cannot tell you.
- Clear writing, attentive listening and dependable follow-through across a team. A student initiative, research project or event can demonstrate these habits.
- Technical curiosity about software, APIs, data and AI-enabled workflows; enough understanding to ask useful questions and learn from engineers.
Useful exposure
SQL, dashboards, process mapping, user research, project tools or a small automation are useful. An MBA, project-management certification, account-management experience and previous people-management responsibility are not prerequisites.
04 / HOW YOUR OWNERSHIP GROWS
Learn in the work.
Grow through the feedback.
Start by maintaining an outcome tracker, coordinating a bounded deliverable or investigating an adoption barrier. Progress towards running a small outcome workstream with senior review across planning, rollout and measurement. Develop the judgment to connect technical delivery to business results; resourcing, contractual commitments and people-management decisions remain with the accountable leads.
Explore
Understand the problem and ask useful questions.
Build
Make a defined contribution and learn through review.
Own
Take on broader responsibility as your readiness grows.
05 / THE DEVX CULTURE
The principles
show up in the work.
Understand what the customer is trying to change. Ask the extra question, surface the real obstacle and connect your work to their goals.
A feature shipped, but the workflow is still slow. Stay with the problem and find out why.
Client obsession. Understand what the customer is trying to change. Ask the extra question, surface the real obstacle and connect your work to their goals.
AI-native everything. Use AI to improve how you research, build, analyse and document. Understand its limits, verify the output and handle customer information responsibly.
Hire and train exceptional talent. We bring young talent and experienced practitioners together. Bring ambition, seek direct feedback and put new understanding into practice.
Document to scale. Write down the decision, its context and what you learned. Make your work understandable enough for someone else to continue, question or improve it.
Only ever be honest. Flag risk while there is time to act. Separate what you know from what you assume. Give clear feedback and make uncertainty visible.
06 / START A CONVERSATION
Show us the way
you think.
Share a résumé and one example where you helped a team turn a goal into a result. Coursework and student initiatives count. Explain the baseline, your contribution, how you followed up, the evidence of progress and what you would improve.
Join through an internship with the opportunity to convert to a full-time role. The hiring team will share internship duration, work arrangements, campus eligibility and conversion criteria during recruitment.
An illustrative project
A retailer pilots an AI support assistant to reduce handling time without reducing resolution quality. You could maintain the outcome plan for one enquiry category, coordinate a user trial, track adoption barriers and compare agreed measures against the baseline. If replies are faster but customers reopen more tickets, bring that evidence to the team and help define the next improvement.