86. Managing People

Managing people is not corporate overhead. It is how founders turn individual effort into company execution.

Early founders often avoid management because they want speed, friendship, or low process. But lack of management creates hidden process: confusion, repeated questions, unclear priorities, resentment, and founder bottlenecks. Good management is not bureaucracy. It is clarity plus care.

People do better work when they know what matters, what good looks like, where they stand, and how to improve.

The core management question is: can the founder create enough clarity, feedback, context, coaching, and accountability that good people can do strong work without guessing what the founder wants?

Management Starts Earlier Than Founders Think

You are managing once another person depends on your priorities, decisions, feedback, or context. This may happen at employee number one.

Early management does not need layers. It needs:

Clear ownership.
Clear priorities.
Clear standards.
Regular feedback.
Honest conversations.
Documentation when decisions matter.

If the founder avoids management, employees will invent their own version of the company. That creates drift.

Management basics

Expectations

Expectations should be explicit.

Every person should know:

What they own
What outcomes matter
What standards apply
What decisions they can make
What needs escalation
How success will be reviewed

Unspoken expectations become unfair feedback later.

Use an expectations document:

Area	Example
Role mission	Own customer onboarding for paid pilots
Outcomes	Reduce setup time and document repeated blockers
Decision rights	Can change onboarding checklist; needs approval for product promises
Escalation	Escalate enterprise customer risks same day
Standards	Clear customer communication, accurate notes, no untracked promises
Review	Weekly 1:1 and monthly outcome review

This can be one page. It prevents months of guessing.

Feedback

Feedback should be direct, specific, and timely.

Good feedback:

Names the behavior
Explains impact
Gives examples
Invites context
Defines next action

Bad feedback is vague: “Be more proactive” or “Improve communication.” Say what happened and what should change.

Use the SBI format:

Situation: In yesterday's customer onboarding call...
Behavior: You promised the custom report would be ready this week without checking engineering capacity.
Impact: The customer now expects work we may not be able to deliver, and engineering was surprised.
Next: Before promising custom work, check the implementation scope and confirm internally.

Good feedback is specific enough that the person knows what to do differently.

Priorities

Many performance problems are priority problems.

People need to know:

What is most important this week?
What can wait?
What should be stopped?
What tradeoff should be made?

If everything is urgent, management has failed.

A weekly priority note helps:

This week, the top priority is onboarding the three paid pilots.

Must finish:
- Customer A setup
- Customer B data import
- Customer C training call

Can wait:
- Help center redesign
- New dashboard ideas

Escalate:
- Any blocker that delays pilot activation beyond Friday

Priorities should tell people what not to do.

One-on-ones

One-on-ones are not status meetings. They are for alignment, feedback, coaching, blockers, and trust.

Useful questions:

What is going well?
Where are you blocked?
What feels unclear?
What feedback do you have for me?
What should we change?
What support do you need?

Take notes. Follow up.

Use a 30-minute one-on-one structure:

Person’s agenda.
Priorities and blockers.
Feedback both ways.
Growth or role questions.
Decisions and follow-ups.

One-on-ones are especially important in Indian teams where some employees may hesitate to challenge a founder in group settings.

Reviews

Performance reviews should not contain surprises.

Use reviews to summarize:

Outcomes
Strengths
Gaps
Growth areas
Compensation or role changes, if relevant
Next expectations

In early startups, reviews can be simple but should be regular.

Simple review template:

Section	Notes
Role outcomes	What was expected and what happened
Strengths	What should continue
Gaps	What must improve
Ownership	Where they closed loops or did not
Collaboration	How they worked with others
Customer/company impact	What changed because of their work
Next expectations	What matters next

No one should hear a serious performance issue for the first time in a formal review.

Coaching

Coaching helps people improve judgment.

Instead of only giving answers, ask:

What options do you see?
What tradeoff are you making?
What evidence do you have?
What would you do if I were not here?
What would make this fail?

Coaching builds independent operators.

Coaching is useful when someone has potential and needs judgment. It is not a substitute for clarity. If the person does not know what outcome matters, coaching questions will frustrate them.

Coach on:

Tradeoffs.
Prioritization.
Communication.
Customer judgment.
Stakeholder management.
Problem solving.

Do not coach forever when performance is clearly below the role requirement.

Accountability

Accountability means ownership of outcomes.

It requires:

Clear goals
Clear owner
Clear deadline
Visible progress
Honest updates
Consequences when patterns do not improve

Accountability without support becomes fear. Support without accountability becomes drift.

Support means:

Context.
Tools.
Feedback.
Time with manager/founder.
Clear decisions.
Removing blockers when needed.

Accountability means:

Outcomes are owned.
Misses are discussed.
Patterns have consequences.
Standards are real.

You need both.

Performance

Goals

Goals should connect work to company priorities.

Good goal:

Specific
Owned
Time-bound
Measurable or observable
Connected to customer or business outcome

Bad goal:

“Improve support.”

Better goal:

“Reduce repeated onboarding questions by publishing docs for the top 10 issues and cutting founder escalations from 20 per week to 8 per week by the end of the month.”

KPIs

KPIs help when they describe real outcomes.

Avoid measuring only activity. For sales, calls matter less than qualified pipeline and closed revenue. For support, response time matters, but repeated issue reduction may matter more. For engineering, tickets shipped matter less than product quality and customer impact.

Use role-specific metric mixes:

Role	Activity metric	Quality/outcome metric
Sales	Outreach sent, calls booked	Qualified pipeline, closed revenue, sales cycle
Support	Tickets handled	Resolution quality, repeated issue reduction, CSAT
Engineering	Stories shipped	Reliability, customer impact, maintainability
Marketing	Content published	Qualified leads, conversion, message learning
Ops	Tasks completed	Error rate, turnaround time, process improvement

Metrics should improve judgment, not replace it.

Output quality

Quality is role-specific.

Define what good looks like:

Code quality
Customer response quality
Design clarity
Sales discovery quality
Operational accuracy
Writing clarity
Hiring judgment

Ownership

Ownership means the person thinks beyond the task.

Signs:

Closes loops
Flags risks early
Communicates tradeoffs
Improves the system
Does not wait to be chased

Collaboration

Startups need collaboration without constant meetings.

Evaluate:

Does the person share context?
Do they unblock others?
Do they create drama?
Do they give and receive feedback?
Do they respect other functions?

Improvement plans

If someone is underperforming, name the gap early.

An improvement plan should include:

Specific issues
Expected behavior or output
Support available
Timeline
Review cadence
Consequence if not improved

Do not use improvement plans as a fake ritual after the decision is already made. Be honest.

An improvement plan should be short and concrete:

Issue:
Expected standard:
Examples:
Support we will provide:
Check-in dates:
Decision date:
Consequence if standard is not met:

If trust is gone or integrity is the issue, a long improvement plan may not be appropriate. Use proper legal/HR advice.

Exits

Exits are part of management.

Keeping a poor fit too long hurts the person, team, customers, and company. Handle exits with clarity, documentation, legal compliance, and respect.

For legal and HR matters, use qualified advice.

Handle exits with:

Clear reason.
Documentation.
Respectful conversation.
Final pay and legal compliance.
Access handover.
Customer/team transition.
Reference policy if appropriate.

How you exit people becomes culture. The remaining team watches.

New Manager Trap

Founders often promote the strongest individual contributor into management too early.

Before promoting, check:

Do they want to manage?
Can they coach?
Can they give feedback?
Can they prioritize across people?
Can they represent company context?
Will the team trust their judgment?
What individual contributor work will they stop doing?

Management is a different job. Loyalty and output are not enough.

Founder As Manager

Founders need to manage their own behavior too.

Watch for:

Changing priorities without context.
Giving feedback only when angry.
Assuming people know what you know.
Becoming the bottleneck for every decision.
Avoiding hard conversations until resentment builds.
Hiring senior people and then not letting them own decisions.

Founder management improves when the founder writes more, repeats priorities, and gives feedback earlier.

Management mistakes

Avoiding feedback

Avoiding feedback feels kind but becomes unfair. People cannot fix what they do not know.

Feedback delayed becomes emotional. Give it when the example is fresh.

Micromanagement

Micromanagement often comes from unclear standards or low trust.

Fix by defining outcomes, check-in rhythm, and decision rights.

No context

People make better decisions with context.

Explain customer reality, strategy, cash constraints, and tradeoffs.

No priorities

If priorities change daily without explanation, people stop trusting direction.

Keeping poor performers

Keeping poor performers damages strong performers first.

Good people notice when standards are not real.

Keeping poor performers can also train managers to lower expectations. This hurts culture more quietly than a single bad hire.

Promoting too early

Do not promote someone into management only because they are loyal or strong as an individual contributor.

Management requires coaching, communication, judgment, and accountability.

No documentation

Document expectations, feedback, compensation, role changes, and performance issues. Documentation protects clarity.

India angle

Indian teams may include people with very different exposure to startup norms. Some employees expect hierarchy. Some expect explicit instructions. Some are uncomfortable challenging founders. Some need family confidence around career risk. Notice periods and compensation conversations can be sensitive.

Founders should normalize:

Direct feedback
Written expectations
Asking questions
Escalating blockers
Ownership
Customer exposure
ESOP education
Career conversations

Management is also translation: turning startup ambiguity into enough clarity for people to act.

India-specific management considerations:

Some employees may treat founder words as final orders, even when the founder is brainstorming. Label brainstorm vs decision.
Junior employees may hesitate to say “I do not understand.” Ask them to repeat the plan in their own words.
Families may care about career progression and stability. Career conversations can matter.
Feedback should be direct but not humiliating.
Notice periods mean performance issues must be addressed early, not when replacement is urgent.
ESOP and compensation questions need plain-language explanation.
Remote employees need written norms because they cannot absorb office context.

Management should respect context without lowering standards.

One-On-One Operating System

One-on-ones are not status meetings. Status can be written. One-on-ones are for judgment, blockers, feedback, and trust.

Use a simple agenda:

What is your top priority?
What is blocked?
What decision do you need?
What feedback do you have for me?
What feedback do I owe you?
What should we discuss that is not urgent but important?

Write down decisions and feedback. If nothing changes after one-on-ones, people will treat them as founder theatre.

Feedback Scripts

Founders often delay feedback because they want to be kind. Delayed feedback is usually less kind.

Use direct scripts:

When [specific behavior] happened, it created [specific impact]. I need you to do [new behavior]. Can you repeat back what you are taking from this?

For positive feedback:

The way you handled [specific situation] helped because [impact]. Keep doing that, especially when [future context].

For repeated problems:

We discussed this on [date]. I am not seeing enough change. Let us agree on the next two weeks of expectations and what happens if it does not improve.

Specificity is respect. Vague feedback creates anxiety.

Performance Triage

When performance is weak, diagnose before reacting.

Cause	Founder response
Unclear expectations	Rewrite outcomes and priorities.
Missing skill	Coach, train, or change scope.
Low effort	Give direct feedback and consequences.
Wrong role	Move quickly if another role is genuinely better.
Poor values fit	Act fast; culture damage spreads.
Personal crisis	Be humane while keeping work expectations clear.
Founder management failure	Fix your context, feedback, or decision-making.

Not every performance issue is the employee’s fault. Not every issue can be coached. The founder’s job is to tell the difference early.

People Management Cadence

Management feels heavy when it happens only during problems. Make it a cadence.

Cadence	Practice	Purpose
Weekly	Written priorities and blockers.	Keeps work aligned.
Weekly or biweekly	One-on-ones.	Builds trust, surfaces issues, gives feedback.
Monthly	Role outcome review.	Checks whether the person is succeeding in the actual job.
Monthly	Team health review.	Finds overload, conflict, ambiguity, or culture debt.
Quarterly	Performance and growth conversation.	Discusses trajectory, scope, compensation expectations, and development.
After major projects	Retrospective.	Converts execution into learning.

This does not require HR bureaucracy. It requires rhythm.

Role Clarity Document

For every employee, maintain a one-page role clarity document:

Field	Answer
Role mission	Why this role exists.
Outcomes	What good looks like in 30/60/90 days.
Ownership	What decisions or workflows they own.
Interfaces	Who they work with most.
Metrics	What signals indicate success.
Support	What they need from founder/manager.
Growth path	What expanded scope could look like.
Risks	What could cause underperformance.

The document should evolve. Early startups change, but people still need clarity.

Feedback Timing

Use this rule:

Situation	Feedback timing
Small correction	Same day or next one-on-one.
Customer-impacting issue	Same day.
Repeated pattern	Formal conversation with notes.
Values issue	Immediate and direct.
High performance	Specific praise quickly.
Role mismatch	Discuss as soon as pattern is visible.

Delayed feedback makes problems bigger. It also makes the founder seem unpredictable because the employee hears about old issues suddenly.

When To Exit Someone

Exiting an employee is serious, but delaying forever can be unfair to the company and the person.

Consider exit when:

Expectations were clear and repeatedly missed.
Coaching did not change the pattern.
The role requires a capability the person does not have.
Trust is broken.
Values mismatch is damaging the team.
The founder is keeping the person mainly to avoid discomfort.

Handle exits legally, respectfully, and with documentation. A humane exit is not a soft exit; it is clear, fair, and timely.

Reader action

For each direct report, write:

What they own
What good looks like
Top priority this month
One strength
One growth area
Feedback they need
Support they need

Then schedule one real one-on-one conversation and discuss it directly.

Add a weekly management review:

Person	Priority	Blocker	Feedback owed	Support needed	Risk

This keeps people work visible. If you only manage when something breaks, you are already late.

Management Escalation Ladder

Founders often jump from silence to frustration. Use an escalation ladder instead.

Level	Situation	Founder action	Documentation
1. Clarify	Expectation may be unclear.	Restate outcome, owner, deadline, and support.	Brief note.
2. Coach	Skill or judgment gap appears.	Give specific feedback and examples.	One-on-one notes.
3. Reset	Pattern repeats.	Agree on 2-4 week improvement plan.	Written expectations.
4. Decide	Improvement is insufficient or trust is damaged.	Change role, reduce scope, or exit respectfully.	Formal record with counsel/HR where needed.

The ladder prevents surprise. People should know where they stand before the founder reaches a final decision.

Manager Operating Notes

For every person you manage, keep private operating notes:

Field	Notes
Strengths	What they reliably do well.
Energy	What kind of work gives or drains energy.
Communication	How they process feedback and context.
Current priority	The most important outcome now.
Risk	Where they may struggle.
Support	What the founder owes them.
Next conversation	Topic that should not be postponed.

This is not surveillance. It is memory. Founders hold too much context in their heads, and people deserve managers who remember patterns.

Management Anti-Patterns

Watch for these founder habits:

Giving feedback only when angry.
Changing priorities without explaining tradeoffs.
Praising heroics while ignoring sustainable execution.
Delegating outcomes but keeping all decisions.
Avoiding poor performance because the person is loyal.
Promoting the earliest employee instead of the right manager.
Confusing friendship with management.
Treating quiet employees as fine because they create less noise.

A startup does not need corporate HR to manage well. It needs clear expectations, timely feedback, and humane accountability.

People Risk Review

Every two weeks, review people risk the same way you review product or revenue risk.

Risk	Signal	Founder action
Unclear ownership	Two people think they own the same thing, or nobody does	Clarify owner, decision rights, and output
Quiet underperformance	Person is busy but outcomes do not move	Reset expectations and inspect support needs
Burnout	High output with visible exhaustion or irritability	Reduce load, reprioritize, add support
Founder bottleneck	People wait for founder decisions	Delegate decision rights or create rules
Skill gap	Good effort but repeated quality issue	Coach, train, narrow scope, or redesign role
Trust issue	Bad news hidden, commitments missed, defensiveness	Direct conversation and written reset
Culture damage	One person lowers truth, speed, or respect	Intervene quickly

People risk becomes expensive when founders treat it as soft until it becomes dramatic. Early review keeps it operational.

Delegation Contract

Delegation is not “please handle this.” It is a contract.

For important work, define:

Field	Example
Outcome	Reduce onboarding time from 45 minutes to 20 minutes
Owner	Customer success lead
Decision rights	Can change onboarding email and checklist; needs approval for pricing/policy changes
Constraints	Must not increase support load or break enterprise onboarding
Checkpoints	Review after 5 customers
Success evidence	Time-to-value, user confusion, support tickets, activation
Escalation	Ask founder if customer promise changes

Delegation fails when founders delegate tasks but keep context, authority, and standards. A good delegation contract gives the person enough room to own the outcome without guessing what the founder secretly wants.

Difficult Conversation Prep

Before a hard people conversation, write the prep.

Prompt	Notes
What happened?	Specific behaviour or outcome
Why does it matter?	Impact on customer, team, speed, quality, trust
What pattern, if any, is repeating?	Evidence
What does good look like?	Concrete expectation
What support will we offer?	Coaching, clarity, resources, decision rights
What happens if it does not improve?	Consequence or next review

Use this opening:

“I want to discuss a pattern that is affecting [impact]. My goal is clarity and improvement, not surprise. Here is what I have observed…”

A conversation that feels kind but unclear is not kind. A conversation that feels direct but respectful gives the person a chance to act.

Role Clarity Reset

When performance feels weak, first check role clarity. Many early-team performance problems are actually unclear ownership, shifting priorities, missing authority, or founder context trapped in someone’s head.

Run a role clarity reset before assuming the person is the problem:

Area	Reset question
Outcome	What result is this person responsible for in the next 30-90 days?
Priority	What are the top three priorities, and what should be ignored?
Decision rights	What can this person decide without founder approval?
Inputs	What context, customer access, data, tools, or budget do they need?
Standards	What does good quality look like? Show examples.
Collaboration	Who must they work with, and where are handoffs failing?
Cadence	How often will progress be reviewed?
Escalation	What should they raise early instead of silently carrying?

Use this script:

“Before we judge performance, I want to make sure the role is clear enough to perform. Let us reset the outcome, authority, support, and review cadence.”

After the reset, write the agreement and review it after two to four weeks. If performance improves, the issue was system clarity. If it does not, the conversation can move to skill, effort, judgment, or fit with much better evidence.

People Review Operating Dashboard

Founders often manage people reactively: a problem appears, anxiety rises, and then a heavy conversation happens too late. A simple people dashboard makes management visible before it becomes dramatic.

Review this monthly for every direct report or key early employee:

Area	Green signal	Risk signal	Founder action
Outcomes	Important work is moving	Busy but little progress	Reset priorities and success evidence.
Ownership	Person anticipates issues	Waits for instructions	Clarify decision rights and expectations.
Judgment	Makes tradeoffs well	Escalates everything or hides choices	Coach with examples and boundaries.
Communication	Surfaces risk early	Surprises appear late	Create explicit risk reporting.
Energy	Sustainable pace	Exhaustion, irritability, withdrawal	Rebalance workload and support.
Collaboration	Peers trust the person	Handoffs create friction	Address interfaces, not only attitude.
Growth	Scope is expanding	Role is stuck or shrinking	Discuss path, skill gaps, or fit.

This review should not become secret HR theatre. It is a founder tool for noticing patterns and taking timely action.

One-on-one operating questions

Use one-on-ones for signal, not status reports only.

Good recurring questions:

What is the most important outcome you own this week?
What is blocked that I may not see?
Where are you waiting on me?
What customer/team/product issue is repeating?
What decision do you need more authority to make?
What part of the role is unclear?
What feedback do you have for me?
What are you avoiding because it may be uncomfortable?

Do not ask all questions every week. Rotate them. The point is to keep truth moving.

Founder self-check

Before judging a person, ask:

Did I define the outcome clearly?
Did I give enough context?
Did I delegate authority or only tasks?
Did I change direction without explaining why?
Did I delay feedback?
Did I hire someone for a role the company was not ready to support?

Founders should not blame themselves for every people issue. But they should inspect the system before labeling someone weak.

When to move fast

Be patient with learning. Move fast on trust and values issues.

Move quickly when:

Bad news is hidden repeatedly.
Customers are misled.
Team members are disrespected.
Commitments are made casually and missed casually.
The person creates politics in a small team.
Feedback produces defensiveness but no change.

Small teams cannot afford unresolved trust debt. One strong but corrosive person can teach the whole company that output matters more than truth.

Manager Operating Rhythm

Founder management improves when it has a rhythm. Without rhythm, feedback arrives only during crisis or appraisal season.

Use this simple cadence:

Rhythm	Purpose	Output
Weekly one-on-one	Clear blockers, priorities, feedback, and support.	Notes and next actions.
Monthly role review	Check outcomes, ownership, energy, and collaboration.	Role clarity updates.
Quarterly growth review	Discuss scope, skills, compensation expectations, and future role.	Growth plan or fit conversation.
Incident review	Discuss serious misses quickly.	Repair action and expectation reset.
Recognition habit	Name good work specifically.	Standards become visible.

The founder should not wait for a formal HR system. Early employees learn what matters from what the founder notices, repeats, rewards, and corrects.

Delegation Ladder

Founders often delegate tasks but keep authority. That creates dependency and frustration.

Use a delegation ladder:

Level	Meaning	Founder behavior
1. Do exactly this	Person executes a defined task.	Explain steps and quality bar.
2. Recommend	Person investigates and recommends options.	Ask for reasoning and tradeoffs.
3. Decide with approval	Person chooses, founder approves before action.	Review decision quality.
4. Decide and inform	Person acts, then informs founder.	Focus on outcomes and exceptions.
5. Own completely	Person owns the domain and escalates only material risks.	Step back and review periodically.

For each key role, write which decisions sit at which level. Many management problems disappear when authority becomes explicit.

Feedback That Changes Behavior

Feedback should be timely, specific, and connected to impact.

Use this format:

Situation:
Observed behavior:
Impact:
Expected standard:
Next time:
Support needed:
Review date:

Example:

Situation: Monday customer onboarding call.
Observed behavior: We committed to a custom dashboard without checking product capacity.
Impact: Engineering now has unplanned work and the customer expects a timeline.
Expected standard: Custom commitments need product review before being promised.
Next time: Say we will confirm feasibility and revert by Friday.
Support needed: I will give you a list of safe promises and review language.
Review date: Next two onboarding calls.

This is better than “be more careful.” Vague feedback creates anxiety. Specific feedback creates a path.

Performance Decision Tree

When performance is weak, diagnose before deciding.

Question	If yes	If no
Is the outcome clear?	Check skill, effort, judgment, or support.	Reset role clarity first.
Does the person have enough context and authority?	Review execution quality.	Fix inputs and decision rights.
Is the skill gap learnable in time?	Coach with milestones.	Consider role change or replacement.
Is the issue effort or ownership?	Give direct feedback and deadline.	Look for role mismatch or unclear expectations.
Is trust damaged?	Move quickly and document.	Continue coaching if improvement is likely.
Is the company itself changing faster than the role?	Discuss new role needs honestly.	Keep role stable and measure.

Not every weak performance case is a firing case. Not every coaching case should continue indefinitely. The founder’s job is to be fair, clear, and timely.

Founder-To-Manager Handoff

The first managers fail when founders delegate people without delegating context, authority, or standards. A handoff should be explicit.

Use this handoff note:

Area	What to define
Team purpose	Why this team exists now.
Current priorities	The few outcomes that matter this cycle.
Decision rights	What the manager owns and what still needs founder input.
People context	Strengths, risks, growth needs, and sensitive history.
Quality bar	Examples of work that is good enough and not good enough.
Cadence	One-on-ones, reviews, reporting, escalation.
Founder support	Where the founder will help and where they will step back.

If the founder keeps bypassing the manager, the handoff has not happened. If the manager has responsibility without authority, the role is a trap.

Performance Evidence Pack

Performance conversations should use evidence, not accumulated frustration.

Maintain a simple pack:

Evidence	Example
Role expectations	What the person was asked to own.
Work output	What shipped, sold, supported, resolved, or improved.
Quality examples	Specific work that met or missed the bar.
Collaboration evidence	Handoffs, communication, reliability, team impact.
Feedback history	What was said, when, and what changed.
Support offered	Coaching, clarity, resources, scope changes.
Decision	Continue, change role, performance plan, or exit.

This protects both the company and the person. It also prevents the founder from confusing disappointment with evidence.

Exit With Dignity Checklist

Not every hire works out. A founder should handle exits with clarity and humanity.

Checklist:

Be direct about the decision and reason.
Do not debate the decision in the exit conversation.
Explain notice, pay, access, handover, references, and logistics.
Protect customer, code, finance, and data access.
Communicate internally without humiliation or gossip.
Capture learning: role definition, hiring process, onboarding, management, or stage fit.
Treat the person as someone who may remain part of the ecosystem.

India’s startup world is smaller than it looks. How a founder handles exits becomes part of the company’s reputation.

Founder Management Load Map

Founders often underestimate how many people they are actually managing. Direct reports, contractors, agencies, advisors, candidates, customers, and investors all consume attention.

Map your management load:

Person/group	What they need from founder	Cadence	Risk if ignored
Direct reports	Priorities, feedback, decisions, context.	Weekly or biweekly.	Drift, rework, attrition.
New hires	Onboarding, standards, customer context.	High touch first 30 days.	Slow ramp or wrong habits.
Contractors/agencies	Scope, quality bar, review, payment clarity.	Project-based.	Waste, missed deadlines, ownership gaps.
Managers	Decision rights, escalation support, coaching.	Weekly or fortnightly.	Responsibility without authority.
Critical individual contributors	Context, recognition, blockers, growth path.	Regular one-on-one.	Silent burnout or surprise exit.

If the founder’s management load exceeds capacity, do not simply ask everyone to be more independent. Reduce scope, add structure, appoint owners, or hire/enable a manager.

Management Debt Register

Management debt accumulates when people issues are avoided.

Track:

Debt	Example	Cost
Unclear ownership	Two people think the other owns customer onboarding.	Missed handoffs and blame.
Avoided feedback	Founder is frustrated but has not said it clearly.	Surprise performance conversation later.
No role update	Job changed but expectations did not.	Misalignment and resentment.
Overloaded high performer	Reliable person absorbs every urgent task.	Burnout and dependency.
Weak manager support	New manager gets responsibility without coaching.	Team confusion and attrition.
Culture exception	Brilliant person behaves badly and is tolerated.	Standard silently changes.

Review management debt monthly. Pick one debt to pay down. People problems rarely disappear; they either get addressed early or become more expensive.

Manager Quality Review

As the company grows, founders must inspect manager quality without bypassing managers. A weak manager quietly damages speed, morale, quality, and retention.

Review managers on evidence:

Dimension	Healthy signal	Warning signal
Clarity	Team knows priorities, owners, and quality bar.	Team asks founders for basic direction.
Feedback	People know where they stand.	Problems appear suddenly after weeks of silence.
Decision-making	Manager decides within guardrails and escalates well.	Everything waits for founder approval or surprises founder later.
Talent bar	Hiring, onboarding, and performance standards improve.	Manager tolerates weak behavior to avoid discomfort.
Customer/company context	Team understands why work matters.	Team optimizes tasks without business judgment.
Trust	People surface issues early.	Bad news is hidden or softened.

Use a quarterly manager review:

Manager:
Team outcomes:
People risks:
Decisions handled well:
Decisions escalated too late:
Feedback the manager needs:
Support founder will provide:
Review date:

The goal is not to police managers. The goal is to make management a real craft inside the company, not a title change.

Skip-Level Signal Review

When the team has managers, founders should occasionally hear from people below the manager level without turning into a parallel manager.

Use skip-level conversations to learn:

Question	What it reveals
What is most unclear right now?	Context and priority gaps.
Where does work slow down?	Process, decision, or dependency problems.
What customer or product truth do leaders need to hear?	Signals that may be filtered upward.
What is one thing your manager does that helps?	Manager strengths.
What is one thing that would make your team more effective?	Coaching or system needs.

Do not use skip-levels to secretly reassign work, criticize the manager, or collect gossip. After the conversation, share themes with the manager where appropriate. The founder’s role is to improve the system, not undermine the chain of ownership.