The SEAGULL

Strategy dies in 30 minutes. Watch how.

Your team has been executing on the quarterly plan. Projects are moving. Momentum is building. People are focused. Then the SEAGULL descends. Loud. Fast. Confident. "Why are we doing this? This is wrong. We need to pivot. I have some thoughts."

Thirty minutes later: priorities are upended. The roadmap is questioned. Deliverables shift. Half the team is confused. Then the SEAGULL leaves. Flight rescheduled. They're gone by tomorrow.

What they leave behind: chaos. A team without clear direction. A different problem than the one they "fixed."

The pattern

The SEAGULL is the senior leader who descends from above, makes a hasty decision, and disappears. They fly into your meeting, squawk loudly, drop chaos everywhere, and leave before there are any consequences. By the time you understand what they wanted, they are gone. By the time you implement it, it is outdated. By the time it fails, they are focused on something else.

The SEAGULL operates with no accountability. They make decisions without full context. They commit to timelines they will not own. They propose solutions they will not have to maintain.

The worst part? The SEAGULL often feels like they are being helpful. They are "driving urgency." They are "making bold decisions." They are actually just creating chaos and leaving it for others to clean up.

The real cost

A SEAGULL executive once came to a team I worked with. They had been briefly speaking with a fairly new customer. Based on that lunch, they decided the product needed a complete redesign. Estimated work: six months. The team explained why the redesign was a bad idea. They did not listen - they knew better, their status made them confident.

The team spent six months on the redesign. It failed to gain traction. The executive had moved on to a different priority by then. The team was left holding the bag.

This happens constantly because SEAGULL decisions feel smart at the time. It's only in hindsight that you realise the SEAGULL never owned the consequence.

"I have a quick thought…"

How to survive it

1. Document the drive-by. When the SEAGULL unloads, respond with an email immediately. "Thanks for the input. Here's what I heard: [summary]. Here's what we're executing: [current plan]. Here's the impact of switching: [delay, cost]. Want to adjust?" Make it visible. Make it real.

2. Get clear ownership. Before you pivot a single thing, get clarity. "Are you directly responsible for this decision?" If the new direction doesn't work out, who owns that outcome? They have less conviction when accountability gets personal.

3. Require async re-entry. When a SEAGULL drops a chaotic bomb into a meeting or Slack channel, don't react in real time. Freeze the interaction. Acknowledge with flat neutrality: "Got it. To make sure we execute this correctly, please drop those bullet points into the Notion ticket so the engineering team can estimate the scope shift." SEAGULLs despise friction. Forcing them to transition from verbal hand-waving to written accountability filters out low-conviction noise instantly. If it isn't worth 90 seconds of typing for them, it isn't worth a sprint pivot for you.

4. The 48-hour rule. Don't execute on any SEAGULL pivot for 48 hours. Let the recommendation sit. Often, by day two, the SEAGULL has forgotten about it or moved on to the next fire. Or your team has had time to think and can present counter-evidence. Urgency is rarely real.

5. Establish airspace guardrails. Define explicit operational windows where feedback is valid. If a project is in the final stabilisation phase, implement an air-tight change-lock. Let it be known: After Design Freeze on Tuesday, no out-of-band feedback will be integrated until Version 1.1 goes live. This protects your team from the classic late-stage SEAGULL swoop that derails deployments at the eleventh hour.

6. Starve the spectacle. SEAGULLs fly on emotion and performance. They look for wide eyes, frantic typing, and collective panic because it validates their perceived impact. When they swoop in squawking, maintain corporate stoicism. Treat their interruption as a minor scheduling anomaly. When they realise their storm isn't catching wind, they will rapidly fly away to find a more reactive target.

7. Demand follow-up attendance. "Great idea. You will join us in three weeks to review how it's progressing, right?" Most SEAGULLs will resist. If they commit, they will be forced to own the decision. Most will suddenly realise it was not as brilliant as they thought.

Real talk

The SEAGULL isn't trying to break strategy. They think they're leading. They think they're being responsive. What they're actually doing is making your team irrelevant. If every decision can be overturned by a 30-minute drive-by, why would your team own anything? Why would they think long-term? They'd just be waiting for the next SEAGULL visit to blow everything up.

The SEAGULL creates a culture of anxiety, not agility. Real leadership includes saying no. Real leadership is setting a strategy and defending it. Real leadership is trusting your team enough to let them execute without constant interruption.

The antidote

The systemic antidote is transparent project surfaces. When your timelines, ownership metrics, decision logs, and definitions of success are completely visible across the org, a SEAGULL's critique looks transparently ridiculous to the rest of the room. Clear documentation is an un-swappable radar system: it makes drive-by decisions read as drive-by decisions to everyone present, not as leadership. The SEAGULL stops landing when there's nowhere to hide the squawk.

How this maps to WorkFive

The SEAGULL pattern often emerges in trait signatures with high Assertiveness and high Excitement-Seeking but low Dutifulness. The combination produces a leader who enjoys the deciding but not the following through. WorkFive's Crisis Pilot profile flags the SEAGULL as the failure mode where the high-Pressure-Tolerance pattern degrades from "the person who performs in storms" into "the person who manufactures storms and exits before the rain."