🌏 中文版
Today's Topic
The part of behavioral interviews candidates most underrate is assuming "having a story" is enough — what interviewers are actually listening for is specific behavior in that story, not adjectives. After reviewing more than 48,000 job descriptions in 2026, Pin found a gap worth noticing: communication (53.5%), teamwork (50.5%), and leadership (39.8%) show up constantly in JDs, but conflict resolution appears in only 10.9% of them. That means when an interviewer does ask about conflict or influence, candidates are usually less rehearsed, and the answer reveals their real level more than other question types do. Today pairs STAR with a less commonly used but genuinely useful framework, SBI, to work through a question PMs get asked often: how do you influence people who don't report to you.
Core Frameworks
STAR: build the story's skeleton first
| Step | Content | Common point loss |
|---|---|---|
| Situation | Context and background, specific enough to survive follow-ups | Too vague — the interviewer can't tell if it's real |
| Task | Your role and scope of responsibility | Using "we" to blur your personal part |
| Action | The bulk of the answer — what you did and why you chose it | Listing actions without explaining what you were weighing at the decision point |
| Result | A verifiable outcome, ideally with numbers | Vague results that can't be probed further |
SBI: name exactly what the other person did that forced you to step in
SBI (Situation-Behavior-Impact) was developed by the Center for Creative Leadership as a feedback-delivery tool, but it works just as well for dissecting influence or conflict questions, because it forces you to turn vague complaints like "poor communication" or "they weren't cooperative" into three concrete things: what the situation was, what observable behavior the other person actually showed (not your judgment of them), and what real impact that behavior had.
STAR and SBI aren't competing frameworks — use STAR to frame the whole story, and when you reach the Action step and need to explain why you had to influence this person, use SBI's Behavior and Impact to make their specific behavior and its consequences concrete. The story then stops sitting at a flat conclusion like "I eventually convinced them" and instead shows the interviewer how you observed the situation and judged the moment to act.
Today's Practice Question
The Question
"Tell me about a time you needed to influence a group of people who didn't report to you, to get them to change direction. How did you do it?" (Source: gururo.com's behavioral interview question bank for PM/project management roles, fact-checked against current PMI CCR rules, updated October 2026)
How to Break It Down
- Explain why the other side was resistant: Start with their original position and whatever KPI or pressure they were under. Without this, "how you influenced them" becomes a monologue, and the interviewer can't tell if you actually understood the other side.
- Use SBI's Behavior step to define what you actually observed: Don't say "the team wasn't cooperative" — say "the engineering team pushed this request to the bottom of the backlog for three straight sprints, because they couldn't see the connection to their own OKRs." That level of specificity is what makes it a real diagnosis.
- Name the shared interest or metric you found: How you reframed what you wanted as something the other side already cared about. Finding a number or goal both sides agree on is the line between "influence" and "pushing."
- List what you actually did, not your title: You had no formal authority, so what you had was evidence, allies, or a small bet — for example, a limited-scope experiment that let the other side see a result before committing further. Say exactly what step you took, not "I communicated with them."
- Close with Impact, quantified: How the other person's behavior actually changed, and what verifiable result followed — ideally with a timeframe, so the story can be probed further.
Sample Answer (how you might actually say this in an interview)
Situation and behavior (SBI's Situation + Behavior): "We wanted to push a cross-team data standardization project, but the engineering teams owning three downstream systems left this request out of three straight sprints. Their reasoning was consistent: it wasn't on their OKRs, and every change meant extra testing — all cost, no upside, from where they sat."
What I did (Action, finding shared interest instead of pushing): "Instead of going straight to their managers and applying pressure, I interviewed each of the three downstream teams about their most painful recurring bugs, and found that the two slowest-to-diagnose issues for two of the teams both traced back to the same inconsistent field formats. I turned that into a one-page note — 'if standardization ships, your diagnosis time on these two bug classes drops from about 4 hours to under 1' — and took it directly to the most resistant team's manager, one on one, instead of raising it in a cross-team meeting."
Result (Impact): "That manager put the request into the next sprint on their own. The other two teams saw them move first and followed within the same sprint cycle, so all three teams finished the standardization change inside three weeks. Checking back two months later, average diagnosis time on those two bug classes had actually dropped to around 50 minutes. Since then I've kept one habit: when I need to influence people who have no obligation to listen to me, I go find a pain point they already care about but haven't measured yet, instead of leading with the result I want."
Self-Check List
Use this table to check whether your answer covered the key points:
| Checklist item | Covered? |
|---|---|
| Explained the other side's motivation or pressure for resisting | |
| Used SBI to state a concrete, observable behavior, not an adjective | |
| Named a shared interest or metric both sides cared about | |
| The concrete action was evidence/allies/a small bet, not just "communication" | |
| Impact is verifiable, with a timeframe attached | |
| Bonus: the story ends with a habit or principle you carried forward |
Today's Case
Slack: killing a failed game to bet on the internal messaging tool instead
Stewart Butterfield's team at Tiny Speck spent years building the online game Glitch, and by 2012 it still hadn't found a large enough player base, so they shut it down. But while building Glitch, this distributed team had built its own internal tool for messaging, file sharing, and searchable history — originally called Linefeed. Butterfield's call wasn't to keep patching the game — it was to abandon the gaming business entirely and rebuild that internal tool as a standalone product. On its public launch day in August 2013, roughly eight thousand companies signed up, and the team chose to let the product's usefulness inside individual teams drive bottom-up adoption rather than push it through enterprise sales. Slack was later acquired by Salesforce in 2021 for $27.7 billion.
Interview relevance: This case is a direct fit for "tell me about a judgment call you made that went against what most people expected" or "how did you decide whether to persist or give up." What Butterfield actually demonstrated wasn't stubborn persistence — it was noticing that what the team was genuinely using had diverged from what the plan said, and having the conviction to kill the official plan. If your own practice answer today also has a beat like "my original plan wasn't this, but I saw a different signal," that's the same kind of judgment showing up in a different setting.
Further Reading
- 40 Behavioral Interview Questions With Sample Answers (2026) - Pin — the 48,000-job-description dataset behind the 10.9% conflict-resolution stat
- The SBI Feedback Model: A Quick Win to Improve Talent Conversations - CCL — the original source of the SBI framework, from the Center for Creative Leadership
- Behavioral Interview Questions Reddit: PM & Fit Guide - Soreno — the McKinsey PEI prep logic: build two stories each for conflict, influence, deadlines, and teamwork
This Week's Review
| Day | Topic | Practice question | Self-rating |
|---|---|---|---|
| Mon 11/09 | Product Sense | Zoom AI transcripts tanked attendance — a real Meta interview question broken down with the Human Delta framework | ☐ Done ☐ Needs review |
| Tue 11/10 | Metrics & Analytics | (No output this cycle — no practice recorded) | — |
| Wed 11/11 | Strategy & Execution | (No output this cycle — no practice recorded) | — |
| Thu 11/12 | AI Product Design | (No output this cycle — no practice recorded) | — |
| Fri 11/13 | Growth & Experimentation | A real Slack PM question: finding a new product-led growth loop beyond invites and cross-company channels | ☐ Done ☐ Needs review |
| Sat 11/14 | Technical PM | Stripe's real migration: swapping a verified boolean for a status enum without breaking 200 integrated customers | ☐ Done ☐ Needs review |
| Sun 11/15 | Behavioral | Influencing people who don't report to you: using SBI to make "what they actually did" concrete | ☐ Done ☐ Needs review |
Next Week Preview
Next week (11/16–11/22) stays on the standard rotation with no weighted overrides: Mon Product Sense, Tue Metrics & Analytics, Wed Strategy & Execution, Thu AI Product Design, Fri Growth & Experimentation, Sat Technical PM, Sun back to Behavioral & Weekly Review. Metrics, Strategy, and AI Product Design all had no output this week — if any of those three is already a weak spot for you, consider raising its weight in src/data/interview-focus.json so the routine pulls it on non-default days too.
References
- Behavioral Interview Questions For Project Managers (+ STAR) - gururo.com — source for today's practice question, fact-checked against PMI CCR rules
- The SBI Feedback Model: A Quick Win to Improve Talent Conversations - CCL — source for the SBI section of today's frameworks
- 40 Behavioral Interview Questions With Sample Answers (2026) - Pin — source for the STAR section and the topic's opening statistic
- Top 10 Product Management Case Studies Every Product Manager Should Know - PolarisCampus — source for today's case, Slack's pivot away from Glitch