Agile and hybrid environments often value speed and vocal interaction — but vocal participation is not the same as inclusive participation nor key/sound contribution.
Inclusion must be intentionally designed into workflows. Structured turn-taking, silent brainstorming before discussion, asynchronous updates, and explicit invitations to quieter voices can significantly rebalance influence.
If collaboration relies only on who speaks first or loudest, we risk losing depth, reflection, and diversity of thinking. Agile is about adaptability — and adapting our communication patterns (not only vocal; it can be written) is part of it.
I was prepared to answer an OKR question... Is it just me, or are others seeing two separate questions? The short answer would be no, because not everybody likes or wants to use OKRs.
Regarding the question about vocal communication, I would argue that agile and hybrid favor frequent and transparent communication, regardless of whether it is verbal, written, synchronous, or asynchronous. If you have a "meeting" culture and/or an environment that rewards whomever speaks first or loudest, this often leads to the exclusion of quieter contributors, and is the responsibility of the person leading the meetings, not the project approach.
As project managers, we are responsible for designing communication systems, within our projects, that allow different participation styles. If you know you're not going to get everyone you need to participate to verbally participate during a meeting, talk to them beforehand or after. You don't need to create a new framework; just talk to people. Saving Changes...
Agile and hybrid environments often value speed and vocal interaction — but vocal participation is not the same as inclusive participation nor key/sound contribution.
Inclusion must be intentionally designed into workflows. Structured turn-taking, silent brainstorming before discussion, asynchronous updates, and explicit invitations to quieter voices can significantly rebalance influence.
If collaboration relies only on who speaks first or loudest, we risk losing depth, reflection, and diversity of thinking. Agile is about adaptability — and adapting our communication patterns (not only vocal; it can be written) is part of it.
Hello Michaud, I do agree with you. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Great points. I also see OKRs and KPIs serving different purposes rather than replacing each other.
KPIs tend to measure performance and stability, while OKRs are useful for direction and strategic focus. In many environments, especially in projects and portfolios, both together provide a more balanced view of outcomes and progress.
...
1 reply by Sunday White
Mar 19, 2026 7:09 PM
Sunday White
...
This has been my personal experience with larger companies and startup companies. Both KPI's and OKR's have their place/focus/use outcomes. Applying them strategically, while also (as noted by Aaron Porter) being an aware and empathetic PM that reaches out to ensure all voices are heard and included in the conversation, is what sets a PM apart from someone who just ticks off the task list boxes. Agile/Hybrid requires more communication, but does not define it to be spoken.
Saving Changes...
Sunday WhiteMarketing Project Manager| EntrepreneurPortland, Or, United States
Mar 10, 2026 10:30 AM
Replying to Lissette Indhira Pimentel Sosa
...
Great points. I also see OKRs and KPIs serving different purposes rather than replacing each other.
KPIs tend to measure performance and stability, while OKRs are useful for direction and strategic focus. In many environments, especially in projects and portfolios, both together provide a more balanced view of outcomes and progress.
This has been my personal experience with larger companies and startup companies. Both KPI's and OKR's have their place/focus/use outcomes. Applying them strategically, while also (as noted by Aaron Porter) being an aware and empathetic PM that reaches out to ensure all voices are heard and included in the conversation, is what sets a PM apart from someone who just ticks off the task list boxes. Agile/Hybrid requires more communication, but does not define it to be spoken. Saving Changes...
OKRs focus on outcomes and alignment, KPIs on metrics and performance. In many projects, both coexist—OKRs inspire direction and ambition, KPIs track progress and operational health. Replacing KPIs entirely is rare; more often, OKRs complement them, giving teams purpose while KPIs ensure accountability and clarity. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Great questions. They point to a deeper shift from measuring activity to governing decision quality.
On OKRs versus KPIs, this is not a substitution but a structural complementarity. KPIs act as system constraints, they protect operational integrity and signal when performance drifts. OKRs act as directional intent, they focus attention, stimulate learning and enable adaptation. In project environments, especially hybrid ones, the real risk is not choosing one over the other, but failing to integrate them at the level that matters most: decision governance. KPIs without OKRs tend to drive local optimization and incrementalism. OKRs without KPIs can create ambition without grounding. High-performing systems deliberately connect both to how decisions are framed, challenged and validated over time.
On inclusion, the challenge is indeed systemic, not interpersonal. Many workflows unintentionally privilege speed, confidence and verbal fluency, which filters out reflection and weak signals. That is not just an inclusion issue, it is a decision risk. Designing for inclusion therefore means designing for better thinking. Practical mechanisms help: asynchronous pre-work to surface diverse perspectives, structured rounds or written inputs before convergence, clear separation between exploration and evaluation, and explicit criteria for what constitutes a “heard” contribution. Participation should be measured by contribution to insight, not airtime.
Both questions converge on a single principle. Metrics and communication structures are not neutral, they actively shape what becomes visible, discussable and ultimately decidable. If we take project outcomes seriously, we should audit these systems not for efficiency or alignment alone, but for the quality of thinking they enable or suppress. That is where real performance begins. Saving Changes...
Community Champion
