Why I'm Building ManagerForge Before HireForge, GoalForge, or ProjectForge

There's a version of this company where we build hiring software first. Hiring is urgent, it's expensive when you get it wrong, and every manager I've ever talked to will tell you it's one of their biggest pain points. We could have launched HireForge in year one and had a clean, defensible market. We didn't, and the reason is the same reason that Lattice and 15Five, for all their investment and engineering, still leave managers feeling like they're doing paperwork instead of leading people.

The order is a thesis. If you get the order wrong, you build something that looks complete and functions like a checklist.

The Keystone Isn't What You Think

In architecture, the keystone is the wedge-shaped stone at the top of an arch. It doesn't look like the most important stone. It's often the smallest one. But pull it out and the whole arch collapses, because every other stone depends on it for its position. The arch isn't weak at the keystone because it's small; it's strong because of where it sits and what it does.

The 1:1 is the keystone of management. Not the most visible thing a manager does, not the thing that shows up on a job description, often not even the thing managers think about when they think about being good at their job. But pull it out and watch what happens to everything else.

I've managed hundreds of people across more than three decades, and the pattern I keep seeing is this: the quality of a manager's 1:1s predicts, with uncomfortable accuracy, the quality of everything else they do. Not because 1:1s are magic, but because they're the place where all the other management surfaces either get their signal or don't.

What a Broken 1:1 Actually Costs You

Walk with me through a specific manager. She's competent, well-intentioned, technically sharp. Her 1:1s run 30 minutes every two weeks, and they follow a pattern: the direct report gives a project update, she asks a few clarifying questions, they talk about blockers, and then they both go back to their desks. Everyone leaves on time. Nobody hates the meetings. They're just not particularly useful.

Watch what happens downstream.

When it's time to set goals, she and her direct report have never had a real conversation about what that person actually wants from their career, what energizes them, what they find draining, or what "success in this role" means to them personally. So the goals they set are role-shaped, not person-shaped. They're technically correct and motivationally inert. When the mid-year check-in comes around, the goals feel abstract, and both people kind of know it.

When she's hiring for a new role on the team, she's interviewing for skills she can observe in a 45-minute conversation, because she's never had a 45-minute conversation with her own people that went deeper than project status. She doesn't have a working model of what makes her best people her best people, because she's never been curious enough about them to build one. So her hiring instincts are blunt. She knows what a good answer sounds like in an interview; she doesn't know what good looks like when it's actually doing the work.

When a project starts going sideways, she finds out late, because her 1:1s have trained her people to present status rather than surface problems. Nobody brings her the early signal, because the early signal is messy and uncertain, and her meetings reward polish. So her project oversight is reactive by design.

And when performance review season comes around, she writes feedback she has technically observed all year but never directly shared, about patterns she noticed but never named, strengths she valued but never articulated. Her people read the review and feel surprised by parts of it, even the positive parts, because the relationship didn't make room for that level of directness during the year. The review is accurate. It's still a failure.

None of this is a hiring problem, or a goal-setting problem, or a project management problem. It's one problem, upstream, presenting in four different places.

Why "Complete" Software Is a Trap

The software answer to this manager's situation is usually a platform. You buy something that has a goal module, a 1:1 module, a performance review module, a hiring integration, maybe an engagement survey. It's all connected. It's all in one place. And it solves exactly zero of her actual problems, because her problem isn't that the information lives in different tools. Her problem is that the conversations aren't happening.

The platforms that try to cover everything end up being shallow at each layer because they're optimizing for coverage, not depth. They're building for the buyer who wants to check the box, not the manager who wants to actually get better. And the checkbox manager will always be a bigger market in the short term, which is why the platforms keep building the way they build.

ManagerForge is a different bet. The bet is that a manager who genuinely masters the 1:1 doesn't need us to hold their hand through hiring, because they already know how to have a real conversation with another person under conditions of uncertainty and limited information. They don't need a goal-setting module that prompts them to ask "what does success look like?" because they already ask that question, every week, as a matter of practice. They don't need a project oversight tool to surface early warning signs because their people already bring them the early warning signs, because the relationship makes that safe.

The keystone, when it's strong, distributes load to every other surface. Fix the keystone first.

The Roadmap Is the Argument

HireForge, GoalForge, and ProjectForge are coming. That's not aspiration, it's sequencing. But when we build them, they'll be built by managers who have already done the harder work of developing the relationship infrastructure that makes hiring, goal-setting, and project oversight actually function. We'll build HireForge for managers who are already good at reading people. We'll build GoalForge for managers who already know what their people care about. We'll build ProjectForge for managers whose people already trust them with bad news.

If we built HireForge first, we'd be building it for managers who are still using interviews as the primary tool for understanding human beings, because nobody taught them a better one. That's not the manager we're building for.

The buyers who understand this argument are the right buyers, and they'll wait. The buyers who don't will go find a Notion template or a Lattice seat, and that's genuinely fine, because the product they want isn't the product that will help them. What they want is coverage. What they need is depth.

Start Where the Signal Comes From

Every piece of management information you have about your people, accurate or not, comes through relationship. The quality of your information is a function of the quality of that relationship. The quality of that relationship is built, primarily, in the 1:1.

This is why a manager's hiring instincts get sharper when they fix their 1:1s: they've been practicing the skill of understanding another person's thinking, not just their words. It's why their goal-setting gets more motivating: they know what actually matters to each person on their team. It's why their project reviews get more honest: people bring them real information instead of managed information. It's why their performance reviews stop being surprises: they've been having the review, incrementally, all year.

The 1:1 isn't one feature among many. It's the place where the manager either becomes genuinely useful to another person's career, or doesn't. Everything else we build will be downstream of that.

Fix the keystone first. Then build the arch.