5 Doable Steps to Build Teams That Think

I remember the exact moment I realized what I’d built: I was on a two-week trip, barely checking in, and the business ran smoother than when I was in the building every day. My first feeling was pride. My second feeling, if I’m honest, was something closer to unease. For years I’d measured my value as a leader by how many decisions passed through me. Watching the team move without me forced me to admit that the busiest version of me was never the most useful one.

That trip changed how I think about leadership entirely. A team that constantly waits on you for the next instruction feels productive because everyone is moving. But motion and thinking are two different things. The real win is a team that carries judgment with them into the room when you’re not there — people who ask better questions, own outcomes, and course-correct on their own.

I’ve watched this same realization hit dozens of operators inside Me Plus Ultra. Almost every one of them built their first version of success on being the smartest, fastest problem-solver in the building. That approach works beautifully right up until the business outgrows one person’s bandwidth. After that, the same instinct that got you here becomes the ceiling on everything you’re trying to build next.

Here are five steps that actually build the kind of team that thinks for itself, drawn from what’s worked inside my own companies and inside the Me Plus Ultra community.

Step 1: Hand Out Outcomes, Not Tasks

Every task you assign trains your team to wait for the next one. Every outcome you assign trains them to figure out the path themselves. This shift sounds small, but it changes everything about how people show up to their work.

When you tell someone exactly what to do, you’re the one thinking. When you tell someone what result you need and trust them with the how, they’re the one thinking. Their judgment gets exercised, strengthened, and eventually trusted — by you and by them.

I saw this play out with a young ops lead on my own team years ago. For months, I handed her checklists. She executed them well, but every new situation outside the checklist landed back on my desk. One quarter, I switched tactics entirely — I gave her a target and a deadline, and left the plan to her. Her first version wasn’t the plan I’d have written. It was better in places I hadn’t even considered, because she’d built it from angles I couldn’t see from where I sat.

Try this with one project this week. Instead of listing steps, describe the result you want and the constraints that matter. Then let your team build the plan. The first attempt might look different from what you’d have done. That’s the point. That’s them learning to think in your business instead of just executing inside it.

Step 2: Ask the Question Before You Give the Answer

Great leaders develop a habit of pausing before they solve. When someone brings you a problem, your instinct as the founder is to jump straight to the fix — you’ve usually seen a version of it before, and giving the answer feels efficient. It is efficient, in the short term. In the long term, it teaches your team to bring you problems instead of solutions.

Build the habit of responding with a question instead of an answer. “What have you already considered?” “What would you do if I weren’t in the room?” “What’s the risk you’re most worried about?” These questions cost you thirty extra seconds and give your team a rep at thinking through the problem themselves. Do this consistently, and within a few months you’ll notice something: people start arriving with the answer already worked out, because they’ve learned that’s what gets rewarded.

This one takes real discipline on your end. The urge to just say the answer out loud is strong, especially when you already know it. Every time you resist that urge, you’re making a small deposit into your team’s capacity to think without you — and those deposits compound faster than most leaders expect.

Step 3: Run a Debrief After Every Project

Momentum makes teams want to move straight from finishing one project to starting the next. That instinct feels productive, but it skips the single highest-leverage five minutes in the whole process: the debrief.

A good debrief asks three things. What worked, so we can repeat it deliberately instead of by accident? What would we change, so the next round is sharper? What did we learn about how this team makes decisions together? That third question is the one that actually builds thinking capacity over time, because it turns every project into a leadership lesson for the people who ran it, not just a completed task.

Keep it short. Ten minutes, three questions, written down somewhere your team can revisit. The compounding effect of doing this consistently is bigger than almost anything else on this list, because it turns your team’s own experience into their best training material.

Step 4: Make Accountability Visible

Accountability works best when it’s seen, not just felt privately. Teams that think for themselves are usually teams where progress, ownership, and follow-through are visible to everyone, not just tracked quietly in a manager’s head.

This can be as simple as a shared board where every owner’s name sits next to their outcome, updated weekly in a way the whole team can see. It can be a standing rhythm where people report their own wins and misses out loud, in their own words, rather than having someone else summarize it for them. The visibility itself does the work. When ownership is public, people rise to meet it — partly for pride, partly because the room is watching, and both of those are healthy motivators when used well.

Peer accountability, done right, builds trust faster than any system a manager could design alone. People hold each other to a standard they helped set, which means they actually believe in it. I’ve watched teams inside Me Plus Ultra turn a simple weekly check-in into their strongest cultural asset, purely because everyone could see everyone else’s word being kept — or not — in real time.

Step 5: Trust the Room Before You Have Proof

This is the hardest step, and also the one that makes the other four actually work. Trust that arrives only after someone has proven themselves isn’t trust — it’s a reward you’re handing out after the fact. Real trust is extended a little ahead of the evidence, on purpose, because that’s the only way people ever get the room to grow into bigger judgment calls.

Give someone a decision slightly above their current level, with a real stake attached, before you’re fully certain they’ll nail it. Stand behind their call publicly, even when you’d have made a different one. Debrief it together afterward using step three. This is how confidence actually gets built inside a team — not through pep talks, but through real reps at real stakes, backed by a leader willing to extend trust first.

I think of trust as a muscle you build together, one rep at a time, in front of real consequences instead of hypothetical ones. Every time you extend it a little early and it holds, both of you get stronger — and so does the whole team watching how you handle it.

Building This Takes a Season, Not a Sprint

None of these five steps land overnight, and that’s a feature, not a flaw. A team that thinks for itself is built through dozens of small moments where you hand over a decision instead of taking it back, ask a question instead of supplying the fix, and back someone’s call before you’re certain it’s the right one. Each moment feels tiny. Together, they add up to a team that carries your standards into rooms you’re not in.

That’s the actual measure of leadership: not how much moves through you, but how much moves well without you. Build toward that, one outcome, one question, one debrief at a time, and you’ll end up leading a team that thinks — the kind of team every serious operator is actually trying to build.

We go deep on exactly this at BB&C 12 this October in Louisville — two days built around real leadership mechanics, not theory. Register here.

Scott Joseph is the founder of Me Plus Ultra, a private leadership community for entrepreneurs and executives navigating complexity, scale, and high-stakes decision-making. The group works with founders who are no longer looking for motivation or tactics, but for sharper thinking, better judgment, and environments that demand accountabilit

Scott is the author of ASCENT, a book on how leaders rise by changing the rooms they operate in, and why environment, not effort, ultimately determines growth. Through Me Plus Ultra, he curates disciplined conversations where experienced leaders pressure-test assumptions, challenge one another’s thinking, and leave with clarity they can actually execute.

In addition to leading Me Plus Ultra, Scott has founded and scaled multiple companies, built and exited complex operating businesses, and facilitated thousands of executive-level conversations across industries. His work now focuses on one thing: helping leaders make better decisions when growth makes everything harder, not clearer.