Zoe Clarke 🥉

State the facts from your estimates. Point out dependencies clearly. Suggest realistic alternatives based on points.

List what changed in your scope over the year: new projects shipped, people trained, recurring tasks you now own. Quantify outcomes in simple terms: revenue protected/added, hours saved, error rates reduced, onboarding time shortened. Examples: trained two hires who reached full productivity in 6 weeks instead of 10 (~8 weeks saved total), cut rework tickets from 12/month to 4, delivered X project that saved ~$2k/month in vendor fees. Translate that into a ballpark business value using conservative assumptions, and note time you invest per week. That gives you a clean before/after picture without fluff. Package it in a one-page doc: summary, three numbered outcomes with numbers, and a proposed next step. Propose options that fit a flat org: a title clarification (e.g., Level II or Lead for X area), a compensation adjustment of $X–$Y based on market bands, or a quarterly stipend tied to the ongoing ownership. Ask for a measurable goalpost and a date: if I sustain A, B, C for 90 days, we move to the new level/comp on MM/DD. Acknowledge budget limits up front and suggest timing (phase-in over two pay periods or at the next budget checkpoint). Keep the tone collaborative and data-first, then make a direct ask at the end: I'd like to align my level and pay with this scope.

It's reasonable to push back when the invite has no agenda or clear outcome, when you're not a decision-maker or contributor, or when it conflicts with a high-priority deadline or a deep work block. Also push back on recurring meetings where you're not getting value, anything outside your working hours or time zone, or when the topic is pure status that could be handled async. A quick check is: can you name the decision being made, the input needed from you, and why it can't be done in a doc or Slack thread? If the answer is no, you're safe to ask for clarity or suggest an asynchronous update. For one-way updates, ask to be moved to optional and request notes or a recording instead. Be polite but specific: try something like 'What decision are we making and what do you need from me? Happy to add comments in the doc and skip live if that works.' Offer alternatives or constraints: propose a 15–25 minute timebox, suggest a smaller attendee list, or delegate a teammate who can represent your area. If you need a different time, use the tool's features and add context: in Outlook choose Propose New Time on the meeting request; in Google Calendar open the event and click Propose a new time; include a note like 'heads-down on X until 2 pm'. For recurring invites, ask to be removed until the topic is active for you, or confirm you'll attend only the first 10 minutes for your update. If pushback might be sensitive, align with your manager first so your priorities are backed, and keep your response about tradeoffs and outcomes, not personal preference.