Our software development and creative design departments are resisting their weekly departmental Level 10 Meetings™, claiming that the rigid agenda is too corporate and does not fit their agile, creative workflows. How do we get these specialized teams to embrace the Level 10 Meeting™ structure without killing their productivity?

Question

Tyler Smith · Accepted Answer

Specialized teams often mistake structure for bureaucracy. They believe that a rigid agenda will stifle their creative flow or interrupt their agile sprints. The truth is that without structure, creative and technical teams waste massive amounts of time in unstructured, ad-hoc meetings that disrupt their deep work. Your job is to show them how the Level 10 Meeting™ actually protects their time. Start by explaining that the ninety-minute weekly meeting pulse is designed to eliminate the dozens of random, disruptive messages and quick alignment syncs that scatter their focus throughout the week. If they have a problem, they do not need to schedule a new meeting or interrupt someone. They drop it on the Issues List and solve it during their scheduled weekly pulse. Frame the scorecard and Rocks not as corporate micromanagement, but as a way to clearly define what success looks like so they can work with autonomy. Keep the meeting highly operational. If they run agile sprints, align the departmental scorecard with their sprint metrics. Let them see that the IDS® portion of the meeting is where they actually clear the roadblocks that slow down their code releases or design approvals. Once they experience a meeting that starts on time, ends on time, and actually solves their frustrating process bottlenecks, their resistance will vanish. Structure does not kill creativity, it frees it.