Chief of Staff resources

By Alice Huang, Chief of Staff and operator

• Chief of Staff vs. Integrator: what EOS says about the role - EOS names the Chief of Staff as another title for the Integrator. Here is what the Integrator does, how it pairs with the Visionary, and how to know if you need one.
• How a Chief of Staff runs the EOS Level 10 Meeting (L10), Scorecard and IDS - The Level 10 Meeting agenda, minute by minute, and how a Chief of Staff keeps the Scorecard, Rocks and Issues List running every week.
• The first 90 days as a Chief of Staff: Rocks, the Scorecard and the A+ problem - A 90-day plan for a new Chief of Staff using EOS Rocks and the Scorecard, and a practical filter for the issue that matters most.
• What to do in the first week after a layoff - A practical first-week plan after a layoff: organize paperwork, check official support and choose a manageable next step in your job search.
• Chief of Staff interview questions: prepare evidence, not a script - Prepare for a Chief of Staff interview with real examples of planning, influence, conflict and follow-through, without memorizing invented answers.
• Questions to ask a founder before accepting a Chief of Staff role - Questions to ask a founder about a Chief of Staff role: priorities, authority, access, working style and what success will look like.
• Do you need a Chief of Staff, an executive assistant or an operations lead? - Compare Chief of Staff, executive assistant and operations-lead work before hiring. Start with the problem and give the right work a clear owner.
• How to write a Chief of Staff resume when your title was something else - Translate your real experience into a Chief of Staff resume while keeping titles, dates, results and your contribution accurate.
• How to ask your network for help after a layoff - Ask your network for job-search help with a clear role target, a real strength and one specific request. Includes an adaptable message template.
• A founder-Chief of Staff working agreement you can write on one page - Create a one-page founder-Chief of Staff working agreement covering purpose, outcomes, scope, decision rights and review rhythm.
• Decision log vs. action tracker: stop losing the why and the next step - Keep decisions and actions separate but linked. A simple decision log and action tracker help teams see the reason, owner and next step.
• My First Million for operators: turn an idea into a small test - Use My First Million as a starting point for business questions. Turn an interesting idea into a small test with evidence, limits and a review date.
• Founders podcast for operators: learn from a biography without copying it - Use the Founders podcast to ask better operating questions. Keep historical context, podcast interpretation and your own application separate.
• How to explain a layoff in an interview without oversharing - Explain a layoff in an interview with a brief, truthful account, then connect your actual experience to the role. No invented restructuring story.
• A job-search tracker that tells you what to do next - Build a simple job-search tracker with a role link, stage, last contact and next action. Keep useful search notes separate from official reporting requirements.
• How to build a Chief of Staff portfolio without sharing confidential work - Create a Chief of Staff portfolio using permitted evidence or clearly labelled fictional work samples. Show judgment without exposing employer information.
• How to approach a Chief of Staff take-home assignment - Approach a Chief of Staff take-home with a clear decision, checked instructions, visible assumptions and a recommendation you can defend.
• Chief of Staff resume bullets: show your part in the result - Write Chief of Staff resume bullets that name the work, your responsibility and a supported outcome, without taking credit for the whole team.
• Chief of Staff or operations manager: compare the actual work - Compare Chief of Staff and operations-manager roles by scope, decision rights, recurring responsibilities and success measures, not title alone.
• How to run a listening tour as a new Chief of Staff - Run a Chief of Staff listening tour with consistent questions, careful notes and a synthesis that separates facts, interpretations and open questions.
• A weekly founder briefing that makes decisions easier - Write a short weekly founder briefing around changes, decisions, risks and next steps. Keep facts, estimates and requests distinct.
• How to turn a vague founder idea into a project brief - Turn a founder idea into a project brief with a problem, evidence, outcome, scope, owner and decision gate before committing the team.
• How to hand work off without becoming the team's reminder app - Make a useful handoff with a clear outcome, accepting owner, decision limits, support and check-in plan. Follow the exceptions instead of every task.
• All-In for operators: separate a market view from a company decision - Use All-In as a source of business questions, not automatic instructions. Separate commentary, checkable claims and company decisions.
• Moonshots for operators: turn a technology forecast into a question - Use Moonshots with Peter Diamandis to frame technology questions. Check forecasts against present capability before making a commitment.
• A founder-focused podcast listening guide: pick the show for the problem - Compare seven business-relevant podcasts by the question you want to answer: ideas, history, strategy, market views, technology or interviews.
• A podcast notes template that ends with one useful action - Keep podcast notes with a source, checked timestamp, claim type, context and one next question. Separate the speaker's words from your action.
• How to measure Chief of Staff work without claiming every team win - Measure Chief of Staff work with agreed outcomes, baselines and clear ownership. Distinguish activity, contribution and company-wide results.
• A stakeholder map for cross-functional work - Build a stakeholder map around who decides, contributes, does the work and is affected. Verify needs and choose a communication plan.
• How to escalate a blocked project without surprising the founder - Raise a blocked project with facts, impact, options and the decision needed. Separate uncertainty from confirmed delay.
• How to review a project before taking on the next one - Review a project using evidence, the team's experience and a small set of owned changes before starting the next round of work.
• How to choose one priority when everything feels urgent - Choose a priority by checking the outcome, deadline, dependency and tradeoff. Name what must wait instead of pretending everything can come first.
• The first founder-Chief of Staff check-in: agree on what good looks like - Use the first founder-Chief of Staff check-in to agree on purpose, outcomes, access, authority and the next review before adding work.
• Acquired for operators: study the business model before the headline - Use Acquired's company histories to ask how a business worked. Keep the source, context and your own operating hypothesis separate.
• The Diary Of A CEO for operators: separate an interview insight from advice - Choose relevant business interviews from The Diary Of A CEO. Check context and evidence before treating an insight as advice for your company.
• David Senra's interview show: what to ask a living founder - Distinguish David Senra's interview show from Founders, then turn a conversation into better questions about decisions and context.