Module 3 · 30 min

S — Status

Perceived place in the hierarchy. The most sensitive dimension and the most often accidentally threatened — in refinement, demos, prioritization meetings, and stakeholder presentations.

You'll learn

Recognize when Status is threatened in daily BA/PO interactions
Reframe feedback (specs review, retro, demo) without triggering defensiveness
Build daily habits that feed your team's Status

Status isn't about title. It's about how others see me and how I see myself compared to them. An innocent comment on your story — „it's not clear what you meant here” — can be read as „you're making me look unprofessional in front of the team”. That shuts people down instantly.

How Status shows up for BA/PO

For BAs and POs, Status is exposed in many daily arenas: refinement (clarity of stories and AC), backlog grooming (justifying priorities), sprint demo (did it deliver what you promised?), retros (your decisions get analyzed), stakeholder presentations (do you actually understand the domain?), workshops (did you facilitate well?). Each is a public evaluation.

What activates Status (toward)

Public recognition for a specific contribution („Ana, your detailed story for the checkout flow saved the team 2 sprints of rework”) — not generic („thanks team”).
Being consulted before a scope decision that affects your team.
Getting a task that validates your expertise („you have the best domain view — can you drive this?”).
Seeing your feedback applied in story refinement — and mentioned („per Ana's suggestion, we split this into 2 stories”).

What threatens Status (away)

Short and directive comments on stories or specs („not like this”, „rewrite”) — without context.
Being corrected by someone more junior, publicly, in stand-up or shared Slack channel.
Seeing someone else get credit for a decision you proposed first.
Not being invited to prioritization decisions where your team is directly affected.
Receiving specs with „step-by-step” instructions on things you can decide yourself.
Demo done by someone else for what you delivered (even „on behalf of the team”).

Exercises — pick what to try

Exercise5 minSoloEnergizer

4 Status moments in BA/PO life

Which of the following scenarios most threatens Status? Pick your answer, then „Check”.

Scenario 1

In demo, the manager interrupts: „Ana, this scope doesn't match what we discussed. How did that happen?”.

Scenario 2

Junior dev leaves a comment on your story in Jira: „I don't think this is well-phrased, it should be rewritten”.

Scenario 3

Tech Lead edits your story directly in Jira (title, AC) without telling you. You see it when reassigned.

Scenario 4

In planning, the EM doesn't invite you — only the Tech Lead. You find out from post-meeting notes.

Exercise8 minPairRedesign

Redesign: a brutal comment on your story

Below is a comment a Tech Lead left on your Jira story. Technically correct — but it triggered Status. Rewrite it to keep the content (the real problem) without hitting Status.

Before
Acceptance criteria are clearly wrong. Validation missing, no error states mentioned, not a word about rate limiting. How do you expect us to build without these?

Write your version — then see a hint and a suggested rewrite.

Your version

Exercise5 minSoloReflection

When was your Status threatened at work?

Note here a recent moment (last 30 days) when your Status got hit. Notes stay in this browser — they aren't sent anywhere.

Recall: a refinement, demo, retro, stakeholder presentation where you physically felt „I'm not being seen well now”. What was said exactly? Why did it land?

Your notes stay only in this browser.

Follow-ups

What would you have wanted said differently? In what setting (1-1 vs. public)?
Who else in that room noticed what you felt? Did you talk to them afterwards?
This week — are you about to say something similar to someone? How do you reframe?

Deep dive (optional)

Mini-check

You need to tell a PO that a user story is ambiguous. What do you pick?

Select an answer.