Notes on ‘The Effective Manager’ by Mark Horstman and How I Run Teams

Verdict: this book gets the two outcomes that matter to executives – hit the targets and keep the talent. I agree with the core formula and I run it with clear numbers, a weekly cadence, and a bias for future behavior.

The scope of the book is narrow. A large portion argues for 1:1s. The opening and closing sections are the payload: results first, then retention; four manager behaviors; and simple, repeatable tools.

What the book gets right and how I apply it

Results are the first responsibility. I ask for explicit, quantified expectations, then publish how I will be measured. That unlocks focus and fast tradeoffs. I expect the same clarity for my directs.

Retention is the second responsibility. Effective leaders deliver and keep people. I treat retention as a managed KPI, not a byproduct. Turnover without performance lift is a miss.

Four behaviors that compound. Know your people. Communicate about performance. Ask for more. Push work down. These behaviors create trust, speed, and scope. I wire them into the operating rhythm from week one.

1:1s the way executives actually benefit

Cadence: 30 minutes weekly, owned by the direct, scheduled at the same time, never skipped. Ten minutes the direct leads, ten minutes I lead, ten minutes for the future. I announce the change in a staff meeting so the rules are transparent.

Why it matters: 1:1s are not status. They are where trust is built, roadblocks surface early, and expectations change quickly without theater. Phone 1:1s only when travel or remote status requires it.

Information flow: broad updates cascade in a weekly staff “waterfall” so I do not repeat the same speech seven times. 1:1s stay personal, specific, and future focused.

Documentation: work lives in a shared repo I can access without asking. If the org cannot see it, it is not done. That simple rule raises quality and speed.

Feedback that changes future behavior

I use one model and I use it often:

• Ask for permission
• State the behavior
• State the impact
• Ask to continue or change

The aim is not to re-litigate the past. It is to shape what happens next. If I am angry, I do not give feedback. I give positive feedback early to set norms, then mix in redirecting feedback once trust exists. Patterns trigger systemic feedback with clear consequences.

When a direct gets defensive, I don’t debate – when that happens, it means the manager already fired a shot across their bow. The question is whether behavior changes. That is the only test that matters.

Coaching that creates durable growth

Coaching is for commitments missed or for stretching top performers. We co-create a plan with DBQ structure:

• Deadline
• Behavior to demonstrate
• Quality standard

I break work into visible, short-cycle deliverables with reporting built in. Progress is discussed briefly in 1:1s and via lightweight updates, not long memos. Four months is a healthy horizon; less is usually a feedback problem, not a coaching problem.

Delegation that scales the team and frees executive bandwidth

Delegation is not task assignment. It is handing off a responsibility I normally own, after I have mastered it. I do not delegate the big new thing my boss just gave me. I learn it, prove it, then hand it down with clear scope and controls.

My pattern:

• I would like your help on X
• Why it matters to the business
• Do you accept
• Context, deliverable, quality bar, deadlines, and reporting

People who choose yes tend to own outcomes. I match responsibilities to what a direct is good at, likes, needs, or wants to learn. That is how you build leaders, not just finish tasks.

What I reject

Micromanagement is not standards. Micromanagement is process control and real-time correction that replaces the person doing the work. I set standards, acceptance tests, and inspection points. I do not sit on someone’s shoulder.

I also reject vague roles. If objectives and yardsticks are unclear, managers cannot allocate time or make smart tradeoffs. I ask four questions on day one: what results, what measures, what objective standards, what subjective factors round out the review. Then I publish the answers.

The operating rhythm I run

Weekly staff meeting: top-line numbers, decisions due this week, risks, owners, and deadlines. Common messages flow here once, not seven times.

Weekly 1:1s: trust, performance, and the future. The direct goes first. My notes are short and actionable.

Feedback all week: in the moment, face to face or on video, with the four-step pattern. Patterns trigger systemic feedback.

Coaching plans: DBQ structure, short-cycle tasks with reporting, reviewed in 1:1s.

Delegation: responsibilities flow down only after I can teach them. Quality and reporting are explicit.

Where I go beyond the book

I add a finance layer: every team runs with quantified goals, a decision log, and an allocation memo template. We tie performance conversations to future behavior and business outcomes, not personality. We use retention and manager quality as real KPIs, not slogans.

I also push clarity on data access and transparency. If leaders cannot see the work product without asking, cycle time and trust both suffer. That is a fixable management problem, not a tooling problem.

UPDATE – Since publishing this post, I have created a page here to summarize my management principles.