Demanded proper advance coordination for customer meetings involving engineering
Situation
Pushed back strongly on a Volvo customer meeting that appeared on calendar at 5pm the day before. Demanded that important customer meetings involving senior engineering staff be scheduled with proper advance notice and coordination.
Reasoning
Enforcing a principle: important customer interactions require planning, not scrambling. Binary framing forces sales/BD to categorize honestly — if important, plan ahead; if not, don't burn senior engineering time. Protects engineering capacity from unplanned demands. Still engaged constructively after setting the boundary.
Additional Context
Meeting showed up on Peter's calendar at 5pm the day before with senior engineering staff included. Peter still participated but established the principle for future interactions. Told Max he didn't need him there and wanted to train the org to go through him.
Observed Evidence
Direct quote from Peter establishing clear boundary. Follow-up messages show Peter still engaged constructively ('its totally ok. Ill make sure people are prepped') while setting future expectations. Also told Max he didn't need him there — protecting his team's time.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
slack
Im far from comfortable with the way this Volvo meeting today has been coordinated with engineering. It showed up on my calendar yesterday at 5pm.
slack
I wanna train the org to talk to me about these things not reach past me to people that work for me.
Outcome
No outcome recorded yet.
Decision ID: 7bc5d77a-44c8-4182-aa05-1d7b5684897d