Communication
67 bites tagged Communication — interview questions with model answers, and 60-second explainers.
Quantify the cost of not addressing technical debt to a Product Owner
Model debt as velocity tax; forecast delays; map time to revenue; scope a slice. Turning tech drag into business cost a PO can weigh against features. Calling it ugly without delivery risk data.
How does 'Individuals and interactions' shape team structure and communication?
Say teams should be cross-functional and favor direct communication like pairing and standups over mandated tool workflows. If you know Agile values human collaboration above rigid systems.
Bar Chart vs. Line Chart for Market Share Comparison?
This tests your grasp of visualization fundamentals for categorical vs. time-series data. A bar chart is correct for comparing discrete categories (companies) at one point in time. A line chart wrongly implies a trend. Red flag: justifying a line chart.
When is a pie chart an appropriate visualization?
Tests your grasp of data viz principles for part-to-whole data. A good answer defines this use case (e.g., market share), then lists pitfalls like too many slices or comparing multiple pies. A red flag is defending pie charts for complex data.
Individuals & Interactions Over Processes & Tools: Explain This Value
Tests your grasp of Agile's core philosophy: empowering people over rigid systems. A great answer defines the principle, links it to cross-functional team structures, and champions direct communication over ticket-passing.
How would you visualize three years of monthly revenue?
This tests your grasp of time-series visualization and data integrity. A strong answer picks a line chart, insists on a zero-based Y-axis and clear labels, and adds context like seasonality.
How do you handle a critical blocked task?
This tests your proactivity, communication, and ability to manage dependencies. A great answer involves immediate investigation, clear async communication of status and impact, and actively driving the resolution by pulling in the right people.
A bug you wrote is in production. What are your next steps?
Tests ownership, communication, and process under pressure. A great answer prioritizes triage and clear communication with the team/PO before jumping to a fix, then follows up with a retro.
How do you handle an unavailable Product Owner?
Tests your ability to solve process bottlenecks collaboratively. A great answer starts with data, then direct communication with the PO, proposes solutions like office hours, and escalates only as a last resort.
A PBI is vague. How do you get clarity?
This tests ownership and proactive communication. A great answer involves documenting questions in the ticket, engaging the PM and tech lead for a discussion, and updating the ticket with clear acceptance criteria before starting any work.
How do you separate the 'what' from the 'how' with a Product Owner?
This tests your ability to influence and uphold Scrum roles. A great answer focuses on understanding the PO's goal, framing your simpler solution in terms of business value (cost, risk), and collaborating on the path forward.
Individuals and Interactions Over Processes and Tools
Tests if you can apply Agile's core human-centric value. A great answer defines the principle, then links it to concrete team structures (co-located, cross-functional) and communication methods (face-to-face). A red flag is dismissing all processes and tools.
Deception: The Core Concept
Deception is the act of convincing someone of untrue information that the sender knows is false. It's often done for personal gain and relies on the receiver's lack of knowledge about the truth.
"Miller's Law" is Ambiguous and Often Misused
"Miller's Law" isn't one rule, but a name for four distinct, unrelated principles. This ambiguity causes confusion in fields like psychology and computer science.
Objection Handling: Turning Customer 'No's into Trust
Objection handling turns customer feedback into trust, even when you say 'no.' Instead of just rejecting a feature request, you explain the 'why' behind your roadmap.
The Golden Circle: Leading with Why
The Golden Circle is a framework for inspiring action by communicating from the inside out: starting with your purpose (Why), then your process (How), and finally your product (What). It's used to build loyalty by connecting on belief, not just features.
Principle of Charity: Argue the Strongest Case
The Principle of Charity means engaging with the strongest possible version of a colleague's argument, not the weakest. Use it in design reviews to find the best idea, not just to win the debate. The footgun is straw-manning an idea to easily knock it down.
Stakeholder Communication Plan: Who Gets Told What, and When
A stakeholder communication plan is a roadmap for who needs to know what, when, and how. It's used to keep executives, dependent teams, and users aligned on project progress. The biggest footgun is a one-size-fits-all approach; tailor updates to each group.
Public Status Page: Your System's Voice During an Outage
A public status page is a dedicated site for communicating your service's health, turning "is it down?" support tickets into a single source of truth. It's used to report outages, degradation, and scheduled maintenance for public-facing services.
Email Marketing: Your Direct Line to Customers
Email marketing is your owned communication channel, a direct line to customers not controlled by an algorithm. Use it to nurture leads, announce features, or drive sales. The footgun is sending generic blasts instead of segmenting for relevance.
A Design System Newsletter: Make Invisible Work Visible
A design system newsletter makes your team's invisible infrastructure work visible. Use it to announce component updates and share challenges, keeping stakeholders engaged.
Design System Changelogs: For Humans, Not Machines
A design system changelog translates code changes into human-readable impact. It's a curated notice for consumers—not a raw git log. It's essential for communicating new components, token updates, and breaking changes so teams can adopt updates safely.
The Big Idea: Your Presentation's Single-Sentence Core
The "Big Idea" is a single sentence distilling your presentation's core message. It must state your point of view and what's at stake, telling your audience what to know and what to do.
Chartjunk: Less is More in Data Visualization
Chartjunk is visual noise in a graph that doesn't help the user understand the data, like 3D effects or decorative backgrounds. It's common in reports where aesthetics are prioritized over clarity.
Get Communication bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.