{"id":554,"date":"2025-12-09T16:35:12","date_gmt":"2025-12-09T16:35:12","guid":{"rendered":"https:\/\/hitchhikersguidetodesign.com\/book\/?p=554"},"modified":"2025-12-11T17:36:19","modified_gmt":"2025-12-11T17:36:19","slug":"the-executive-seagull-effect-in-action","status":"publish","type":"post","link":"https:\/\/hitchhikersguidetodesign.com\/book\/the-executive-seagull-effect-in-action\/","title":{"rendered":"The Executive Seagull Effect in action"},"content":{"rendered":"\n
\n

Story by Michael Gaigg, Group UI Engineer Manager & UX\/UI Tech Center Lead at Esri<\/a><\/p>\n<\/blockquote>\n\n\n\n

I recall working on a rather complex, spatially-driven enterprise app, a multi-million dollar engagement. Throughout the project, we built a strong relationship with our client by hosting multi-day UX discovery workshops, developing personas, creating experience maps, and producing draft wireframes. These foundational activities helped us align our vision and set the stage for a successful design process.<\/p>\n\n\n\n

Our team conducted multiple iterations of design to refine the app\u2019s user experience. We even ran a usability study on a mock prototype to ensure our solutions met user needs. The outcome of these efforts was a design that instilled confidence, everyone was aligned with our findings and design decisions, and we felt ready to transition the app to development.<\/p>\n\n\n\n

Entering the final design review, I felt confident. The entire team was present, and the meeting seemed straightforward. However, an unexpected participant joined: a VP I had never met before, whom I later referred to as \u201cthe seagull<\/a>.\u201d The meeting progressed smoothly with positive feedback and consensus – until the seagull raised a question about adding a way to close the side panel<\/a>. I had intentionally removed this feature, believing that collapsing the panel was unnecessary since all workflows and tools were embedded within it. I explained my reasoning, emphasizing that introducing a close button would add unnecessary clicks and potential downsides. What I didn\u2019t realize was that the question was more of a request than a genuine inquiry. My decision to resist the change unwittingly broke an unspoken rule. Faced with high stakes in this late stage, I decided not to further challenge the request. I recognized that for the seagull, being acknowledged for their contribution was important, and I chose to let it go for the moment.<\/p>\n\n\n\n

This experience taught me the importance of identifying key stakeholders early in the process and involving them from the beginning. I arranged a one-on-one meeting with the VP, which allowed us to get acquainted and exchange ideas. This interaction transformed our relationship into a productive alliance. Ultimately, the project was a success, the app is now being used by both internal staff and our client\u2019s customers.<\/p>\n\n\n\n

Share your story:<\/h2>\n\n\n