Last updated on February 24th, 2026 at 12:38 am
I was talking to a friend who is working at Amazon a few years ago, and he was telling me that he recently took up the role of a “Single Threaded Leader(STL)”. After my conversation with him, I was left enlightened. It was Amazon that brought Technical Program Management (TPM) and the concept of STL to life.
What is a Single Threaded Leader ?
In essence, a single threaded leader is given a specific problem, a budget, and a timeframe and are expected to deliver results. Think about it this way – the organization identifies a startup idea that may have good potential and hands it out to one person who is then accountable to bring the idea to life. Once a proposal gets an OK to proceed, a single-threaded leader is assigned to it, who may or may not be one of the people who took the lead on bringing the idea forward. Unlike multitasking managers, STLs aren’t pulled in multiple directions. They focus deeply on one initiative, from inception to launch, like a founder building a startup inside a larger organization.
Extract from Forbes Interview with Amazon’s head of Devices, Dave Limp:
“We empower the single-threaded leader to go off and make great things.”
Clearly, the term (coined and, as far as we know, used exclusively at Amazon) is a nod to the programming world and means that the leader isn’t expected to multitask. Similarly, an STL wakes up every day thinking about one thing. And that’s what makes this model so powerful for driving innovation. In Jeff Wilke’s words, this is “someone who wakes up and just worries about that thing.” That’s “super important to how we invent,” Dave Limp insists, because “the best way to fail at inventing something is by making it somebody’s part-time job.” The leader is then able to hire a team, usually beginning with one or two technical people — just enough capacity to begin to get started and begin building the thing.
Article: Forbes, “How Does Amazon Stay At Day 1?”
Why STLs Matter for Innovation
In my opinion, an organization has two choices to get innovation going –
a) Identify someone within the organization who has the capability to take the idea and turn it into a business either generating real dollar value or by providing strategic value to the existing customers base. In this case, an organization like Amazon acts very much like a Venture Capital Fund. They take responsible risks in investing in ideas they believe in. At any given point in time Amazon has over 1000 startups they are working on and evaluating.
b) Buy out an existing startup solving the same type of problem.
Organizations that value innovation and have the tech talent in most cases try to build it themselves. The leaders most often chosen for these roles are battle-tested startup veterans or have led similar types of engagements before.
A typical engagement would be something like launching Amazon Go or something as simple as Amazon Alexa | SKILL BLUEPRINTS. A “Single Threaded Leader” you would be responsible for building something ground up, you will need to roll up your sleeves and hire and manage your team like a mini-startup. Being the CEO of this startup you will own the P&L in most cases and would need to partner with stakeholders (product, tech, operations, finance, sales, marketing) to drive strategy for your startup. You will need to create the go-to-market plan to accelerate growth and the number of customers for a brand new business initiative in a short time frame.
In most cases, these individuals are very comfortable dealing with ambiguity, comfortable making decisions and wearing multiple hats. I have seen TPM, Engineering Managers and most often PM-Ts tasked with such endeavors. As a single-threaded owner, you are trusted to operate with complete independence. You are 100% responsible for bringing an endeavor to life – the buck stops with you. In essence, you are trusted to do whatever you need to do to get the job done.
In most cases, you would see that these are product or business ideas that need to go live to see as soon as possible which means getting something out to the customer’s hands is vital. So building something scrappy is fine as long as it fulfills the customer need.
This approach allows organizations to:
- Avoid diluted ownership
- Move faster with fewer dependencies
- Foster innovation through clear accountability
The STL Mindset for TPMs
So what does this mean for Technical Program Managers?
While not every TPM is formally assigned as an STL, adopting the STL mindset can dramatically increase your impact:
- Own the outcome: Don’t just manage the timeline—own the success metrics.
- Focus deeply: If you’re spread across too many projects, advocate to go deep on one.
- Operate like a founder: Build roadmaps, make tough decisions, and act like the buck stops with you.
- Partner like a business leader: Drive alignment across engineering, product, finance, and ops.
TPMs often deal with ambiguity, drive cross-functional collaboration, and manage delivery. But to lead like an STL is to take it a step further: you lead the mission, not just the project.
What If You Fail ?
What happens if the idea you are trying to bring to life fails? Remember the Amazon Fire Phone? At its core, organizations learn and grow from failures.
In Jeff Bezo’s own words –
“To invent you need to experiment. If you know in advance it is going to work it is not an experiment. They are inseparable twins, failure and innovation. You have to be willing to fail. It is embarrassing to fail. If I said to you, you have a 10 percent chance at a 100X return, you should take that bet every time. But you still are going to be wrong nine out of ten times. And you are going to feel bad nine out of ten times.”
TL;DR: Actionable STL Takeaways for TPMs
| STL Trait | How to Practice It as a TPM |
|---|---|
| Deep Focus | Limit context-switching; prioritize one initiative |
| Ownership | Track impact metrics, not just milestones |
| Founder Mentality | Build the team, vision, and execution plan |
| Accountability | Lead cross-functional alignment independently |
| Bias for Action | Deliver value early, even if it’s scrappy |
Curious to learn more? Listen to my podcast with David Glick (Walmart exec and former Amazon VP) where we unpack what STL looks like in practice.
Have a nice day!
Also, read – TPM Interview Questions
Are you interested to know more? Check out some amazing posts on the TPM Blog.
Ready to level up your TPM Career?
Unlock your potential as a TPM—master the fundamentals, navigate career levels, and excel in your role.
Frequently Asked Questions: STL
What does being a Single Threaded Leader mean for a TPM?
For a TPM, being a single threaded leader means you are ultimately responsible and accountable for the outcomes of the program/project. It is a higher level role that moves beyond tracking plans, coordinating timelines. You will do everything that you would in the typical TPM role, but also be a key decision maker in the strategy, prioritization and ultimate go/no-go decisions. If you are not the STL – you escalate that to someone else to make the final tie-breaker decision whereas here, you might get the inputs from your executive sponsor or committee but the decision is yours to make/recommend. The buck stops with you. The STL has full ownership of the outcome, including impact and success metrics.Becoming a STL usually means moving up in senior leadership as you interact heavily with your C-suite /executive leaders.
Do TPMs need the STL title to act like a Single Threaded Leader?
No. Even without the formal title, TPMs can adopt the STL mindset by focusing deeply on one mission and treating it as their own business. You don’t have to be a senior leader or assigned a program that requires this to adopt a ‘the buck stops with me’ mindset. Your organization culture might not support STL, so adjust accordingly if it is a matrixed / top down decision making organization. However, you can still control this within your sphere of influence to effect quick decision making, holistic project oversight and prioritization.
How is an STL-style TPM different from a traditional TPM?
A traditional TPM ensures delivery. An STL-style TPM owns the mission, makes tradeoffs, and acts as if the buck stops with them. The STL works backwards from the goal, impact and replies heavily on metrics. They usually have managers and other TPMs overseeing different parts of the program and rolling up updates to them. Programs requiring STLs are usually large, have a critical business goal and usually are reported on frequently to C-suite/executive leaders.
How has the single threaded leader model proved successful?
Context switching slows execution. When a TPM is single-threaded, decisions are faster and accountability is clearer.This concept was introduced by Amazon and has been widely used in multiple companies since. The titles vary and the roles that can take on the STL capability can be TPM, SDM/engineering leader. Usually it is someone who can deal with both business and technical aspects with some level of depth and has excellent communication and decision making skills.
What kind of ownership is expected from TPMs operating like STLs?
Ownership of results, not just milestones. That includes tracking real customer or business impact, not just delivery dates. Additionally, making critical decisions and being the tie-breaker on opposing viewpoints to keep the program moving forward. Usually these decisions will affect the program outcome. It differs from the traditional TPM role where the decision making is escalated to a higher level leader who owns the final program outcome/goal.
How should TPMs handle ambiguity as Single Threaded Leaders?
By making decisions with incomplete data to keep the program moving forward, STLs are trusted to act independently and adjust as they learn. This is why STLs are usually senior leaders with experience making decisions, with a solid understanding of the business, strong product sense and technical ability to dive deep into architecture, decisions, tradeoffs. Usually the STL has a strong core team of leaders who are well versed in these areas to leverage as advisors when making decisions.
How does the STL mindset help TPM career growth?
It positions TPMs as business and product leaders, not just execution partners, which increases visibility and trust.
What happens if an STL-led initiative fails?
Failure is part of the process. For example, companies like Amazon, which heavily use the STL model, view failed experiments as learning that strengthens future innovation. Not all companies view this the same. Failure is highly visible and the company culture determines how it is viewed. With excellent communication, buy-in and transparency to leaders at all stages of the program and at critical inflection points, a Single Threaded Leader can soften the impact to their reputation and frame it from a business perspective as well as minimize the impact by failing fast and limiting blast radius.
What is the biggest takeaway for TPMs from the STL model?
Act like a founder. Own the problem, focus deeply, make hard decisions, and take responsibility for the outcome.
Interesting that “Amazon” is just discovering this now. Single threaded leaders are the default over on the AWS side of the house. We mostly don’t have “engineering leaders” for example. The title is “Software Development Manager/Director/etc.” and the expectation is that you own the entire business opportunity, not just the engineering bits, even if engineering is the bulk of what you’re concerned with. TPMs may grow into this role, but that usually requires moving out of the TPM role. (Also part of the reason that principal TPMs are rare at AWS. Beyond a certain level, you have to own the team to effectively deliver.)
The best way to doom a strategic initiative is to make it someone’s part-time job. Yet this is exactly what happens most of the time!
Much of my own career has been as a single-threaded leader starting new lines of business, new markets, and new strategic partnerships for established companies to grow and diversify their revenue (though we didn’t use the term STO). So when I saw this trend emerge from Amazon, I knew there was something to it.
nice one Gerard.
Great article, very interesting concept. Looking forward for the podcast on this topic.