Trade Months of Debate for a Direction You Can Defend

What It Is

A focused research engagement that turns a stalled “what do we build” into a product direction your team can act on. It does the strategic and market research a build-focused team isn't set up for, and delivers the result as artifacts that plug into how your designers and engineers already work.

It's the Product Strategy stage of The Fieldway System: Fieldway Research answers a hard question once, Managed Intelligence keeps it current, and Product Strategy turns the evidence into a validated direction – including a clear read on what to pursue and what to leave alone.

What You Get

A connected set of artifacts, not a slide deck – each one handed to the person who'll use it, each tracing back to evidence.

• One or two behavioral personas.Not demographics – how the audience actually decides, what they're trying to get done, what they'll pay for. Detailed enough that your designers can design for them without guessing.
• A problem inventory – 15 to 20 validated problems in five or six themes. Specific enough that an engineer can estimate them, and clear enough that you can finally tell a real problem from a loud request.
• A prioritized roadmap, mapped to those problems. Every item traces back to a problem worth solving – so the backlog stops being a wish-list and starts being a plan.
• A market-intelligence guide. The competitive and market picture the recommendation rests on – grounded in the field, not the loudest voice in the room.
• Go-to-market recommendations. How to actually reach the new audience, not just what to build for them.

Two more, because a direction only counts if the team believes it: I present the whole thing live, so it lands as shared conviction instead of a document you have to sell internally – and I stay reachable for 30 days, in whatever channel you work in, while the team gets moving.

How It Works

The principle is diagnose before you prescribe, applied to what to build. Most of the research volume runs through an AI-augmented method I've refined over years; the judgment – what's a real problem versus a loud one, which market has the TAM to matter, what the evidence actually supports – is mine, and I own the recommendation.

That includes recommending againstthings. Knowing what not to build is worth as much as knowing what to build: a killed bet is a quarter you don't lose. I'll tell you when the math doesn't work, even when it's the option you were hoping to hear yes on – that's the whole point of an outside read.

What It Isn't

It isn't a strategy deck.You've seen those – a firm spends three months and hands you slides that look sharp and connect to nothing your engineers can build. This is the opposite: personas your designers can design for, problems your engineers can estimate, a roadmap you ship against. The recommendation is the point, not the PowerPoint.

It isn't a senior hire.Bringing in a Head of Product to “own strategy” means months of ramp while the bet stays open – and the hire inherits the same internal blind spot you have. This is external, method-driven, and it can de-riskthe hire: you'll know the direction the role is stepping into before you fill it.

It isn't another round of experimentation – which is the objection worth taking head-on.

“Can't we just build our way to it?”

It's a fair question, and it comes from a real strength: your team ships, and shipping has always been how you learn. So here's the honest answer. Experimentation is how you sharpen a direction you already have. It can't hand youone. Telemetry tells you what people did, never why – and when engagement is thin, there's nothing to read at all. Shipping the wrong thing is still the slow, expensive path, even now that building is cheap; it just feels like progress because something shipped.

None of that means stop building. It means point the building at the right target first. Research is how you do that – so you ship the right thing once, instead of three wrong things and a post-mortem.

And it isn't only about new markets. Whatever the bet – breaking into a new audience, or moving a stuck number on one you already have, like retention or engagement or the task they keep failing – the same gap shows up. With a new audience, the intuition that built your core product doesn't transfer: different people, different problems, different willingness to pay. With an audience you already have, the trap is assuming you already know why the number won't move. Either way, the understanding has to be earned, not assumed – and research is how you earn it fast.

What It Looks Like in Practice

Tallo– a 10-year-old career platform – brought me in to help them reach a new audience. They'd run experiments and talked it through internally, but the traction wasn't coming. The Strategy work gave them a researched path into that market: two behavioral personas, a market-intelligence guide, 15 problems across six themes, feature concepts, and a go-to-market the team could build against. They were shipping a month later, and what they shipped landed right out of the gate.

There was a second audience in play, too – one they were already chasing with features, partner outreach, and standalone programs that weren't working. The research showed why that bet wouldn't pay off, and they wound those programs down to put the energy where it would. That's the part a build-fast team can't do for itself: an outside read that says stop, with the evidence to back it, before another quarter disappears into it.

The trust behind it wasn't cold. Stride – Tallo's parent – first brought me in years earlier as Director of Product, where engineering productivity tripled in 90 days, and I led the technical and feature discovery when Stride acquired Tallo. Tallo came back three years later for a different problem because I had earned their trust by consistently delivering.

They stopped debating and started building toward something they believed in.

What It Costs

Scoped on a call – it depends on the opportunity and how much ground the research has to cover. For context, it's a fraction of what a misdirected quarter of engineering costs, set against a decision that shapes a year of roadmap. I take two of these a quarter.

It comes with a guarantee: if it doesn't deliver actionable strategic direction – personas, validated problems, a prioritized roadmap – you get a full refund. The risk of the bet is real enough; the engagement to de-risk it shouldn't add to it. If you'd rather see the quality first, Fieldway Research is the low-commitment way in.

After the Direction

The direction is the start of the work, not the end of it. Once you have it, many teams keep me on to help execute. That takes a few shapes: staying close as you build, so each new bet gets validated against the research before it costs you a sprint – the ongoing Managed Intelligence layer; guiding the prioritization and scope calls as they come; and, when the thing slowing you down turns out to be delivery rather than direction, hands-on help fixing it in flight. Same diagnose-before-prescribe discipline, now pointed at building the thing rather than choosing it.

That's what the Tallo engagement became: a direction first, then an ongoing relationship that keeps surfacing the next move. It's where the work goes when you want a partner through execution, not only a direction. We scope it on a call.

Who This Is For

You've got a proven product, real revenue, and a team that can execute – and you're staring at a direction bet you can't yet call. Growth has flattened and the board wants a plan, or there's an adjacent market you don't have the internal experience to chart, or you've been going in circles on it for months. The bet is real, and it's yours.

It's not the fit if you're pre-product-market-fit with no proven base to extend from – that's zero-to-one discovery, and it's what Fieldway Researchis for: bring the idea and you'll get a straight read on whether it's worth pursuing and roughly how it'd look, or why it isn't and what I'd do instead. And it can't work if you won't give the research what it needs – access to your users, your market, and your own data; starve it of inputs and there's nothing to ground a direction in.

Frequently Asked Questions