Tallo: From Months of Debate to a Shipping Roadmap
How Tallo replaced months of circular debate with a validated direction – personas, 15 problems in 6 themes, a roadmap, and a clear no on a second market.
Tallo had a 10-year-old career development platform with plateauing growth. Leadership wanted to expand to a new audience but had spent months going in circles internally. The Strategy stage delivered a validated direction – 2 behavioral personas, 15 problems in 6 themes, a prioritized feature roadmap, and market intelligence. One month later, the team was shipping features.
The Challenge
Tallo's platform had served one primary audience successfully for a decade, but growth was plateauing. Leadership saw a clear opportunity: expand to serve 18-20 year olds entering the workforce without a college degree – an underserved population that aligned with Tallo's mission.
The problem wasn't identifying the opportunity. It was figuring out the specifics. Who exactly are these people? What problems do they actually face? What should we build for them? How do we reach them?
The team had spent months trying to answer these questions internally. Strategy sessions produced debate but not direction. Customer research generated signals that contradicted each other. Meanwhile, no one was building anything because no one agreed on what to build.
Leadership was also considering a second potential market. Two possible directions, months of deliberation, and zero clarity on either.
What the Strategy Stage Delivered
I ran systematic market research on both opportunities and delivered a complete direction package.
2 Detailed Behavioral Personas for the Career Starters segment. Not demographic abstractions – deep behavioral and psychological profiles showing motivations, pain points, decision patterns, and what makes this audience choose or reject solutions. Personas the product team could actually design for.
Market Intelligence Guide covering competitive dynamics, opportunity sizing, and positioning strategy for the career services and workforce development space. The context the team needed to make smart execution decisions.
15 Specific Problems organized into 6 major themes. These weren't vague problem statements – they were specific, researchable, buildable problems that drove feature prioritization directly.
Initial Feature Concepts mapped to each problem, prioritized by impact and feasibility. The team could start design spikes and engineering feasibility work immediately.
Go-to-Market Recommendations for reaching the Career Starters audience and validating direction as they build.
A Recommendation to NOT Pursue the Second Market. The research showed insufficient total addressable market. This single finding saved Tallo from months of wasted engineering, design, and leadership time chasing an opportunity that wasn't there.
The Outcome
The contrast tells the story clearly.
Before: months of internal uncertainty. No agreement on who to target. No clarity on what problems to solve. No consensus on what to build. Nothing shipping.
Two weeks in: a complete direction. Personas. Problems. Roadmap. Market intelligence. A clear "yes" on one market and a clear "no" on another.
One month in: detailed roadmap for the next quarter. Team actively shipping features against the new direction.
For comparison: while Tallo's team began executing on research-backed direction, another internal team at the same company spent 4 months with no discovery completed, no work defined, and nothing shipped. Same company, same resources, different approach.
Months of circular debate were replaced by systematic research and a clear path forward.
The Backstory
This wasn't my first engagement with this team.
Three years earlier, Stride – Tallo's parent company – hired me as their Director of Product Management for Career-as-a-Platform. Their product team was 5 months behind schedule with an 80% defect rate. In my first couple of weeks I diagnosed the root causes and implemented the fixes, and the team tripled their productivity within 90 days.
During that original engagement, we evaluated and acquired a company called Tallo. I led the technical and feature discovery process for the merger, mapping how the platforms could fold together.
Three years later, Tallo brought me back – this time not for delivery, but for direction. Where I once worked out how they built, I now worked out what they should build. The fact that they came back after three years, for a completely different type of problem, says something about the trust built during that first engagement.
That's the kind of long-term relationship this work creates. You solve the real problems, and clients come back when new ones emerge.
Current status: Tallo has extended the contract multiple times. I'm helping them execute the roadmap, running additional research, developing direction for other feature sets and audiences beyond the original remit, and making continuous prioritization decisions as they build. As of July 2026, the roadmap is built out through April 2027.
Frequently Asked Questions
What did the Strategy engagement deliver?
Two behavioral personas, a market-intelligence guide, 15 validated problems across 6 themes, initial feature concepts mapped to those problems, go-to-market recommendations, and a recommendation against pursuing a second market. Tallo's team had a detailed execution roadmap within a month.
Did Tallo have product managers on staff?
Yes. Strategy isn't about replacing your team – it's about giving them the research foundation they couldn't build from inside. Tallo's team was great at execution. They needed the research, personas, and problem framing to know what to execute against.
What if my company hasn't been around for 10 years?
The method works for any company with a proven product considering adjacent-market expansion. A 10-year track record gave Tallo more data to work with, but the research – market study, persona development, problem inventory, roadmap creation – applies regardless of company age.
Does the engagement end once the direction is set?
It doesn't have to. Many teams keep me on through execution – prioritization calls, scope questions, and further research as new questions surface. When the thing slowing a team down turns out to be delivery rather than direction, that gets handled inside the same engagement. Tallo has extended several times, and as of July 2026 the roadmap is built out through April 2027.
What does the ongoing work actually look like?
Helping the team execute the roadmap, running additional research, developing direction for feature sets and audiences beyond the original remit, and making the continuous prioritization decisions that emerge when you're actually building. Scope has expanded from the original audience and feature set into new research, new audiences, and new directions. It's a separate engagement that typically starts as a 3-6 month commitment.
More Case Studies
- Stride: 3x Productivity in 90 Days – the engagement I ran for Tallo's parent company three years earlier
- CoinDesk: 9-Month Delays to 3x Productivity – turning around delivery at a cryptocurrency media company
Ready to Get Strategic Clarity?
The Strategy stage of The Fieldway System turns a stalled "what do we build" into a validated direction your team can build against – personas, a problem inventory, and a prioritized roadmap, including a clear read on what not to build.
Book a discovery call, or email matthew@fieldway.org.
Ready for similar results?
Tell me the question you're trying to answer, and we'll find the right place to start.
Book a Call