{"id":128,"date":"2026-06-24T23:37:21","date_gmt":"2026-06-24T13:37:21","guid":{"rendered":"https:\/\/www.gokhanmeric.com\/blog\/ui-ux-playbook-ux-governance\/"},"modified":"2026-06-24T23:43:31","modified_gmt":"2026-06-24T13:43:31","slug":"ui-ux-playbook-ux-governance","status":"publish","type":"post","link":"https:\/\/www.gokhanmeric.com\/blog\/ui-ux-playbook-ux-governance\/","title":{"rendered":"UI\/UX Playbook Part 4: UX Governance"},"content":{"rendered":"\n

This is Part 4 of the complete UI\/UX Playbook<\/a>. Strategy and interface craft matter little if the team can’t work together effectively to deliver them. UX governance describes how teams of people with different skills and specialisms should collaborate to produce the best user experience. Two truths frame this entire part: developing a digital product is a complex process, people are complex beings \u2014 and the only certainty in a project is change.<\/p>\n\n\n\n

The Management Approach: Waterfall vs Agile<\/h2>\n\n\n\n

There are two broad approaches to collaboration on a project. The Waterfall<\/strong> approach offers a more comfortable management experience, while the Agile<\/strong> approach minimises risk and produces a far better UX outcome.<\/p>\n\n\n\n

In Waterfall<\/strong>, because the work passes between teams of different skills and people, knowledge and experience must be very well documented and handed to the next team. Testing is generally done toward the end of the project. Roles \u2014 strategy specialists, content UX, back-end\/front-end developers, UI\/UX, testing, QA \u2014 work in sequence.<\/p>\n\n\n\n

In Agile<\/strong>, cross-functional teams collaborate every sprint. This is typically around 5\u20139 people fully dedicated to a project, ideally sharing the same location. Testing happens as part of every sprint. A user-focused Agile approach produces an excellent UX outcome \u2014 which is why it’s the recommended default in this playbook.<\/p>\n\n\n\n

Methodologies in Detail<\/h2>\n\n\n\n

Waterfall<\/strong> is a classic development process \u2014 linear and sequential with a fixed scope. It carries high risk when time, innovation, and budget changes come into play, because it’s hard to change long-term plans when user needs or technology evolve.<\/p>\n\n\n\n

Agile<\/strong> uses an incremental, iterative approach. A core feature set is defined, then short sprints are planned and developments are made progressively, with features added along the way. From the project’s core structure through all its sprints, work is completed by people with mixed skills from all teams. UX work can be done both while building the core structure and in every sprint \u2014 producing a product with a good user experience and high usability.<\/p>\n\n\n\n

Failure Risk<\/h2>\n\n\n\n

The two approaches distribute risk very differently.<\/p>\n\n\n\n