Solve Your Urgent Customer Experience Challenge. Build Permanent Capability.
+$1M
The pattern you've seen before
Every engagement ends with a report. Rarely with a team that can repeat it.
You've been through consulting cycles. A firm comes in, assesses the situation, delivers the deck, and leaves. Six months later, you're back at the same crossroads — the institutional knowledge walked out the door with the consultants.
Your team did everything right. They participated in the workshops, reviewed the deliverables, and nodded along to the methodology. But when the engagement ended, so did the capability. The work was done to your team, not with them.
And now you're weighing another engagement. You need results this quarter. But you also know that another engagement is just more budget for a problem that resurfaces in a different form next year.
You're not looking for a consultant. You're looking for a way out of a pattern that's not working.
A different kind of engagement
Four weeks of focused work — and your team comes out the other side knowing exactly how to do it again.
This is what the HCD Implementation Sprint is designed to produce: a solved problem and a capable team. Not one or the other.
When the engagement ends, your team has a 120-day implementation roadmap with clear success metrics. They have documented methodology they tested against a real challenge. They have the HCD Guide Series — every volume — as a permanent reference. And they have firsthand experience applying systematic human-centered design to work that matters to your organization right now.
The next time a similar challenge surfaces, they don't need to escalate it or hire out. They know the process. They've run it.
If you're thinking: "We've tried methodology training before and it didn't stick" — that's exactly the point.
Most methodology training fails for the same reason: the team learns concepts in a structured setting and then returns to real challenges with no bridge between the two. The learning and the work stay separate. The methodology never becomes muscle memory.
The sprint is structured differently. Your team doesn't learn the methodology and then apply it later. They apply it to a live organizational challenge in real time — with Ishmael Interactive working alongside them. The methodology sticks because it was never separated from the work in the first place.
By the time the engagement ends, your team doesn't need to remember what they learned. They've already done it.
Who runs the engagement
Ishmael Interactive was built on one insight: organizations don't have a strategy problem. They have a capability problem. Knowing what to do and having the institutional muscle to do it consistently are very different things.
The HCD methodology behind this sprint was developed over 20 years of private- and public-sector practice. In the private sector, that means organizations like Condé Nast, Universal Studios, and Apple — environments where speed, consumer demand, and competitive pressure required a methodology that could move fast without losing rigor.
If you're thinking: "We've tried methodology training before and it didn't stick" — that's exactly the point.
The full systematic implementation of that methodology was then proven at federal scale: nine years across seven agencies, including GSA, VA, CDC, and NASA. Implementing this system, these organizations saw record-breaking trust score increases (VA), produced $11 million in documented cost savings (GSA), and generated over $1 million annually for the Lab at OPM. This is the body of work became the standard CX, DX, innovation, and process improvement framework across those agencies.
This engagement transfers that methodology directly to your team. Not through a slideshow. Through doing the work together.
The sprint structure
Four weeks. One prioritized challenge. A team that finishes stronger than it started.
Each week of the engagement is designed to build on the last — moving from strategic clarity to implementation foundation to long-term capability.
Week 01
Strategic Assessment
- Stakeholder interviews to surface organizational blockers
- Current-state analysis of your customer research maturity
- Priority problem identification using the HCD framework
Week 02
Implementation Roadmap
- Detailed 120-day action plan with clear success metrics
- HCD framework customized to your organizational context
- Capability transfer session with your core team
Week 03
Implementation Foundation
- Change team identification and alignment
- Intensive sessions on the full scope of the roadmap
- Targeted workshops in your highest-risk implementation areas
Week 04
Sustainment Training
- Medium and long-term planning and goal-setting
- Co-design of your impact measurement tool
- Primary data analysis and documentation handoff
What your organization walks away with
A solved problem on your desk — and the systematic capability your team needs to stay ahead of the next one.
At the end of four weeks, here is what changes for your organization.
A comprehensive assessment report with prioritized opportunities, ready to present to leadership.
A 120-day implementation roadmap with documented success metrics your team owns and understands.
Case studies and documentation built from your actual work, usable for ongoing internal reference and stakeholder communication.
The complete HCD Guide Series for every sprint participant — so the methodology stays inside your organization permanently.
A trained change team that has practiced the methodology on a real challenge and can apply it again independently.
An impact measurement tool co-designed for your context, so you can demonstrate ROI in terms that matter to your leadership.
Zero consultant dependency when the engagement ends — by design.
Two directions from here
The challenge on your team's desk right now is not going to wait for the right moment.
You have two options, and both are genuine choices.
Path A
Continue as-is
- The challenge stays unresolved or gets escalated
- A future engagement solves it — and leaves no lasting capability
- Your team continues to rely on external expertise for similar problems
- The cycle repeats
Path B
Solve it — and own the process
- The challenge is addressed with systematic rigor in four weeks
- Your team learns the methodology by running it on real work
- Future challenges don't require an outside engagement
- Your organization is more capable — not more reliant — when the sprint ends
Common questions
Everything you need to make a clear decision.
How disruptive is this to our team's existing workload?
The sprint is designed to work on your highest-priority challenge — meaning the work your team does during the engagement is work they need to be doing anyway. We're not adding a side project. We're providing a structured, systematic approach to a problem that already deserves focused attention, across four dedicated weeks.
We don't have a formal HCD practice. Is this the right starting point?
Yes. The sprint is specifically designed for organizations that want to build capability from the ground up — or reset and formalize an existing informal practice. You don't need prior HCD experience. The methodology is systematic and teachable, and the engagement is structured so that learning happens through doing.
What if our team resists the process?
Resistance is common, and it's accounted for in the sprint structure. Week 3 includes targeted workshops in your highest-risk implementation areas, and the change team identification process in Week 3 is specifically designed to create internal advocates. Teams tend to engage differently when they're working on a real challenge rather than a hypothetical exercise.
What happens after the four weeks?
The 120-day implementation roadmap, the impact measurement tool, and the full HCD Guide Series remain with your team permanently. The goal of the sprint is to leave your organization fully capable of running similar processes independently. If you choose to work with Ishmael Interactive again on a new challenge, that's a choice you make from a position of capability, not necessity.
How do we know if the sprint is right for our organization?
The discovery call will answer that. We'll spend 30 minutes assessing your current challenges, your team's readiness, and whether the sprint structure is the right fit for your context. If it's not, we'll say so. The engagement only works when it's matched to the right organizational moment.
One more thing
The organizations that benefit most from this engagement are the ones that are tired of renting expertise — and ready to own it.
If that sounds like your team, the discovery call is the right next step. It's 30 minutes to determine whether this is the right engagement for your most urgent challenge.
If it's not the right fit, you'll know that too — clearly, and without the runaround.
See if we're the right fitFree 30-minute call. No cost or commitment.
