After the keynote: choose one seam to examine

After a keynote, the most useful move is often modest: choose one seam and examine it carefully.

A seam is a place where work leaves one group and depends on another. It might be sales to implementation, product to engineering, technology to operations, finance to a business unit, or one regional team to another. Keep the unit of attention small enough that people can recognize it. A whole function is too broad. A recurring handoff, decision, approval, escalation, intake request, or shared customer commitment gives leaders something concrete to inspect.

Name the shared outcome next. Focus on the result both teams are trying to make possible, not only the activity each side performs. A practical statement might sound like this: "A customer change request is understood, sized, approved, and scheduled without being reopened three times." The sentence does not need to be perfect. It gives both teams the same object to look at.

Then notice the friction without turning the exercise into employee surveillance. Look for waiting, rework, repeated clarification, duplicated checking, decision reopenings, and escalation. These are signals about the work system and the relationships inside it. They are not a scorecard for blaming individuals.

Ask both teams what they believe is happening. One side may describe missing information. Another may describe late involvement, unclear decision rights, competing goals, or incentives that make local optimization safer than shared progress. Listen for the gap between the explanations. When the stories do not match, the seam is probably carrying more translation work than anyone planned.

Sort the likely causes before choosing a repair. Some problems are technical: the tools, data, or workflow do not support the work. Some are structural: priorities, roles, measures, or decision rights are unclear. Some are relational: people do not yet have enough reliability, candor, or shared context to move quickly when pressure rises. Many seams contain more than one pattern. Naming the pattern helps leaders avoid an expensive fix for the wrong problem.

Agree on one small repair with a clear owner. You might create an earlier review point, define what ready means, clarify a decision rule, shorten an escalation path, or decide what information must travel with the work. Keep the repair small enough to try within a week.

Review one observable signal after that week. Did waiting decrease? Did clarification happen earlier? Did a decision stay decided? Did escalation become less necessary? A single repair will not prove a theory or guarantee a gain. It will show whether the seam became easier to work across and whether the people involved now share a clearer view of the work.

For a short conference companion, complete the BRMConnect survey and download the digital Field Guide. For a fuller application path, see The Invisible Tax: Practitioner's Field Workbook.