WEBVTT 00:00:00.000 --> 00:00:03.379 Welcome to the debate. Today we're tackling a 00:00:03.379 --> 00:00:05.639 really foundational tension. It's derived from 00:00:05.639 --> 00:00:08.080 the material parking lot ideas versus ship it 00:00:08.080 --> 00:00:10.859 now. And we're diving into the professional etiquette, 00:00:10.859 --> 00:00:13.960 really, and the efficacy of managing those valuable, 00:00:14.119 --> 00:00:16.960 sometimes disruptive, non -agenda ideas that, 00:00:16.960 --> 00:00:19.359 well, they inevitably surface during focused 00:00:19.359 --> 00:00:22.059 collaborative meetings. Right. And the central 00:00:22.059 --> 00:00:24.480 question we're facing, I think, boils down to 00:00:24.480 --> 00:00:27.739 priority. Is the best professional standard to, 00:00:27.739 --> 00:00:30.600 you know, rigidly adhere to the parking lot mechanism 00:00:30.600 --> 00:00:34.320 to preserve the sanctity of the agenda? Or should 00:00:34.320 --> 00:00:37.619 we prioritize a kind of ship it now action to 00:00:37.619 --> 00:00:40.700 capitalize on creative momentum and frankly velocity? 00:00:40.909 --> 00:00:42.990 And I'll be arguing that discipline, structured 00:00:42.990 --> 00:00:46.170 idea parking isn't just some mechanism. It's 00:00:46.170 --> 00:00:49.590 really the essential social contract for groups. 00:00:49.810 --> 00:00:52.329 It's necessary for maintaining focus, managing 00:00:52.329 --> 00:00:54.490 that collective attention, and preserving what 00:00:54.490 --> 00:00:57.049 I like to call decision hygiene. And I'm going 00:00:57.049 --> 00:01:01.189 to argue that prioritizing immediate but constrained 00:01:01.189 --> 00:01:05.170 action soul velocity over strict order is actually 00:01:05.170 --> 00:01:08.069 superior for driving real progress. It helps 00:01:08.069 --> 00:01:11.079 avoid organizational paralysis. and maybe most 00:01:11.079 --> 00:01:15.040 importantly ensures we respect the perishable 00:01:15.040 --> 00:01:17.560 nature of a creative breakthrough when it happens. 00:01:18.239 --> 00:01:22.920 Okay, so structure, I believe structure is paramount 00:01:22.920 --> 00:01:26.340 because, well, time is the only commodity we 00:01:26.340 --> 00:01:29.359 really cannot manufacture. Parking discipline 00:01:29.359 --> 00:01:32.280 isn't just process. It's about respecting the 00:01:32.280 --> 00:01:34.939 group's collective energy. That discipline, it 00:01:34.939 --> 00:01:37.159 acts as a crucial social contract, doesn't it? 00:01:37.500 --> 00:01:39.840 It ensures people feel heard while preserving 00:01:39.840 --> 00:01:42.480 the meeting's intended outcome. I mean, we've 00:01:42.480 --> 00:01:44.719 all been in meetings where every tangent gets 00:01:44.719 --> 00:01:48.640 airtime and the whole thing just derails. Parking 00:01:48.640 --> 00:01:51.099 the idea, it reduces that cognitive overload 00:01:51.099 --> 00:01:54.599 and helps secure a clean outcome. And importantly, 00:01:54.840 --> 00:01:57.519 it signals true psychological safety. People 00:01:57.519 --> 00:02:00.099 feel heard, and they trust the ideas captured 00:02:00.099 --> 00:02:03.159 with intent for future action, not just dismissed 00:02:03.159 --> 00:02:06.739 out of hand. Hmm. I acknowledge the need for 00:02:06.739 --> 00:02:10.479 focus. Absolutely. But we need to address the, 00:02:10.479 --> 00:02:14.099 let's call it the psychological reality of deferred 00:02:14.099 --> 00:02:17.240 hope. Because in practice, the parking lot, well, 00:02:17.500 --> 00:02:19.960 it rarely functions as that perfectly positive 00:02:19.960 --> 00:02:22.969 memory system you describe. Real organizational 00:02:22.969 --> 00:02:26.110 progress, I think, favors immediate small wins. 00:02:26.509 --> 00:02:29.310 You know, excessive parking leads almost inevitably 00:02:29.310 --> 00:02:32.370 to this massive backlog bloat that just kills 00:02:32.370 --> 00:02:35.990 urgency. When valuable ideas are constantly deferred, 00:02:36.189 --> 00:02:38.830 the parking lot becomes, well, the later graveyard. 00:02:39.370 --> 00:02:42.490 It signals organizational apathy, really. That's 00:02:42.490 --> 00:02:45.229 a strong image, the graveyard. It is, because 00:02:45.229 --> 00:02:48.310 I think it reflects reality in many places. The 00:02:48.310 --> 00:02:51.389 most toxic insight a contributor can draw is 00:02:51.389 --> 00:02:53.530 that their best ideas, the ones they're excited 00:02:53.530 --> 00:02:56.150 about now, are simply not important enough to 00:02:56.150 --> 00:02:59.330 warrant resources now. And over -structuring, 00:02:59.430 --> 00:03:02.229 it ultimately pushes teams into analysis paralysis, 00:03:02.409 --> 00:03:04.710 doesn't it? Where the search for perfect order 00:03:04.710 --> 00:03:08.009 becomes a kind of stalling tactic. Conversely, 00:03:08.229 --> 00:03:10.069 I mean, nothing validates effort like shipping 00:03:10.069 --> 00:03:12.889 something. Velocity is morale for many teams. 00:03:13.370 --> 00:03:16.550 Okay. So, we agree on the need for some structure, 00:03:16.750 --> 00:03:19.689 but we diverge on the priority, it seems. Is 00:03:19.689 --> 00:03:22.250 the sanctity of the agenda more valuable than 00:03:22.250 --> 00:03:24.789 capitalizing on a, as you put it, perishable 00:03:24.789 --> 00:03:28.250 moment? My position remains that focus is the 00:03:28.250 --> 00:03:30.409 highest professional etiquette in these collaborative 00:03:30.409 --> 00:03:33.689 settings. The parking lot ensures promising ideas 00:03:33.689 --> 00:03:36.870 aren't lost. It captures that value without hijacking 00:03:36.870 --> 00:03:39.569 the immediate agenda. Think about sprint planning 00:03:39.569 --> 00:03:42.840 for a critical checkout flow. the team must finalize 00:03:42.840 --> 00:03:45.300 that immediate high -stakes deliverable. Now, 00:03:45.300 --> 00:03:48.219 if a brilliant idea for a, say, pricing revamp 00:03:48.219 --> 00:03:51.259 surfaces right then, parking it, capturing its 00:03:51.259 --> 00:03:54.080 essence, assigning an owner, scheduling maybe 00:03:54.080 --> 00:03:56.740 a discovery session next Wednesday, that protects 00:03:56.740 --> 00:04:00.280 today's necessary high -stakes outcome. It's 00:04:00.280 --> 00:04:02.879 triage, really, in real time. But the cost of 00:04:02.879 --> 00:04:05.460 freezing that moment, that might outweigh the 00:04:05.460 --> 00:04:07.860 benefit of the focused output you're aiming for. 00:04:08.139 --> 00:04:11.340 Flow matters just as much as strict focus, I'd 00:04:11.340 --> 00:04:14.000 argue, especially when you're working on innovative 00:04:14.000 --> 00:04:17.319 systems or features. When a genuine breakthrough 00:04:17.319 --> 00:04:20.160 idea emerges mid -meeting, just confining it 00:04:20.160 --> 00:04:22.720 to a written note, well, that can kill the creative 00:04:22.720 --> 00:04:26.339 spark. Creativity is perishable. If that pricing 00:04:26.339 --> 00:04:29.319 idea is hot, maybe we should strike now, but 00:04:29.319 --> 00:04:32.339 with constrained action. Contrast your approach 00:04:32.339 --> 00:04:35.180 with, let's call it, the velocity model, instead 00:04:35.180 --> 00:04:37.589 of parking the revamp until next week. Maybe 00:04:37.589 --> 00:04:41.110 we initiate a 40 -hour spike. A spike, just for 00:04:41.110 --> 00:04:43.389 clarity, is a really time -boxed investigation. 00:04:43.990 --> 00:04:46.310 Maybe one or two developers prototype the core 00:04:46.310 --> 00:04:49.930 idea to figure out feasibility and impact quickly. 00:04:50.389 --> 00:04:52.430 While the rest of the team finalizes the checkout 00:04:52.430 --> 00:04:55.290 flow as planned, the spike team generates an 00:04:55.290 --> 00:04:58.930 answer on the pricing idea. This action, it respects 00:04:58.930 --> 00:05:02.370 the emergent value and it might unlock a faster 00:05:02.370 --> 00:05:05.959 win. It turns a week's delay into a 48 -hour 00:05:05.959 --> 00:05:08.860 discovery. That 48 -hour spike is interesting, 00:05:09.339 --> 00:05:11.819 but... Well, it brings me to accountability, 00:05:11.899 --> 00:05:14.480 actually, because this is where the ideal system 00:05:14.480 --> 00:05:17.120 of parking lots. It often breaks down in the 00:05:17.120 --> 00:05:19.839 messiness of organizational reality. I think 00:05:19.839 --> 00:05:22.180 we have to design processes that account for 00:05:22.180 --> 00:05:25.160 human nature, for how things actually work, not 00:05:25.160 --> 00:05:28.319 just academic ideals on paper. If the organizational 00:05:28.319 --> 00:05:30.600 culture won't diligently maintain a pristine 00:05:30.600 --> 00:05:33.000 system, and let's be honest, often it won't, 00:05:33.040 --> 00:05:35.680 than parking equals forgetting. It just does. 00:05:36.319 --> 00:05:39.339 So we have to favor immediate small slices of 00:05:39.339 --> 00:05:41.639 shipping because realistically people trust what 00:05:41.639 --> 00:05:43.860 gets done now far more than what's scheduled 00:05:43.860 --> 00:05:45.839 for later in some perpetually growing backlog. 00:05:46.339 --> 00:05:49.660 Okay, that raises a critical challenge. Organizational 00:05:49.660 --> 00:05:52.579 compliance or maybe just discipline. But I think 00:05:52.579 --> 00:05:55.360 we must distinguish between a bad parking lot 00:05:55.360 --> 00:05:58.189 and a good one. the abuse you described that 00:05:58.189 --> 00:06:00.889 ghost backlog, the graveyard. That happens when 00:06:00.889 --> 00:06:03.750 no one curates it, no one owns the items, no 00:06:03.750 --> 00:06:06.850 one maintains a revisit cadence. That, to me, 00:06:06.930 --> 00:06:09.829 is a failure of process maintenance, not an inherent 00:06:09.829 --> 00:06:12.930 flaw in the concept itself. A good parking lot 00:06:12.930 --> 00:06:15.610 is a living system. It demands high fidelity. 00:06:15.990 --> 00:06:19.230 It acts as focus with memory. For instance, every 00:06:19.230 --> 00:06:21.910 parked item must immediately have defined fields, 00:06:22.230 --> 00:06:24.949 a clear title, and explanation of why it matters. 00:06:25.160 --> 00:06:27.660 you know, the business value, an owner assigned 00:06:27.660 --> 00:06:30.160 to shepherd it forward, maybe a tentative due 00:06:30.160 --> 00:06:33.060 date for resolution, and critically, a concrete 00:06:33.060 --> 00:06:35.860 next step, like schedule 30 -minute discovery 00:06:35.860 --> 00:06:38.860 next Tuesday. The failure to include these concrete 00:06:38.860 --> 00:06:41.399 feels, that's what leads to the cynicism and 00:06:41.399 --> 00:06:43.399 the feeling of apathy you correctly identified 00:06:43.399 --> 00:06:46.879 earlier. OK, so you're saying the implementation 00:06:46.879 --> 00:06:50.519 is often the problem, not the idea of the parking 00:06:50.519 --> 00:06:53.740 lot itself. Precisely. Furthermore, rigorous 00:06:53.740 --> 00:06:57.649 parking Done well facilitates crucial risk triage. 00:06:58.129 --> 00:07:01.149 It's necessary for separating high, medium, and 00:07:01.149 --> 00:07:04.029 low value ideas, and perhaps more importantly, 00:07:04.610 --> 00:07:07.050 distinguishing reversible versus irreversible 00:07:07.050 --> 00:07:10.389 decisions. You know, etiquette for managing risk 00:07:10.389 --> 00:07:13.350 demands we don't allow a shiny tangent, however 00:07:13.350 --> 00:07:16.269 exciting, to derail a critical path activity. 00:07:16.589 --> 00:07:19.329 Take a nonprofit board meeting, for example. 00:07:19.670 --> 00:07:22.389 If the annual gala logistics have an immediate, 00:07:22.790 --> 00:07:25.350 calendar -dependent deadline, parking an excellent 00:07:25.350 --> 00:07:27.509 but tangential discussion about implementing 00:07:27.509 --> 00:07:31.470 a new donor CRM is, well, it's absolutely necessary. 00:07:32.189 --> 00:07:34.110 Discipline requires protecting that critical 00:07:34.110 --> 00:07:37.189 path, especially when external deadlines or maybe 00:07:37.189 --> 00:07:40.310 regulatory compliance are involved. Hmm. The 00:07:40.310 --> 00:07:43.430 pressure to protect the internal calendar? That's 00:07:43.430 --> 00:07:46.180 a powerful incentive I grant you. But we have 00:07:46.180 --> 00:07:48.779 to recognize that opportunity costs, it cuts 00:07:48.779 --> 00:07:51.860 both ways, doesn't it? The longer the delay on 00:07:51.860 --> 00:07:54.680 a potentially valuable idea, the more market 00:07:54.680 --> 00:07:57.480 advantage we might cede to competitors, or the 00:07:57.480 --> 00:07:59.579 more critical external windows we might just 00:07:59.579 --> 00:08:02.439 miss. Etiquette for impact, I'd argue, means 00:08:02.439 --> 00:08:05.180 respecting the customer or the donor by delivering 00:08:05.180 --> 00:08:08.420 value sooner rather than later. So in your nonprofit 00:08:08.420 --> 00:08:11.240 board case, what if a critical donor matching 00:08:11.240 --> 00:08:15.000 window closes in just 10 days? Approving a lean 00:08:15.000 --> 00:08:18.199 pilot tier for that CRM immediately, a kind of 00:08:18.199 --> 00:08:20.480 ship -it -win focused solely on servicing that 00:08:20.480 --> 00:08:23.160 specific donor cohort, that could deliver impact 00:08:23.160 --> 00:08:26.139 within that tight window. Delaying until after 00:08:26.139 --> 00:08:28.699 the gala might mean sacrificing a core mission 00:08:28.699 --> 00:08:31.040 delivery goal. The truly professional choice, 00:08:31.079 --> 00:08:33.159 maybe, respects the constraint of the external 00:08:33.159 --> 00:08:35.559 opportunity even above the comfort of the internal 00:08:35.559 --> 00:08:38.220 agenda. That's a fair challenge on opportunity 00:08:38.220 --> 00:08:41.330 cost. And I fully acknowledge your point that 00:08:41.330 --> 00:08:44.649 we must avoid organizational chaos, absolutely. 00:08:45.389 --> 00:08:48.509 But ship now doesn't have to equate to chaos. 00:08:48.830 --> 00:08:51.370 It requires disciplined action through let's 00:08:51.370 --> 00:08:53.950 call them guardrails. We don't have to choose 00:08:53.950 --> 00:08:56.909 between paralyzing structure on one hand and 00:08:56.909 --> 00:09:00.009 wild abandon on the other. We can propose methods 00:09:00.009 --> 00:09:02.570 where immediate action is tightly constrained. 00:09:02.909 --> 00:09:05.870 This means explicitly defining ship at guardrails 00:09:05.870 --> 00:09:08.450 for any emergent idea that gets the green light 00:09:08.450 --> 00:09:11.549 for immediate, limited action. Things like a 00:09:11.549 --> 00:09:14.129 firm time box. Maybe it is that 48 hours for 00:09:14.129 --> 00:09:17.009 a spike. A clearly defined success metric. What 00:09:17.009 --> 00:09:19.750 does a good outcome actually look like? And most 00:09:19.750 --> 00:09:23.070 critically, a mandatory revert plan. If this 00:09:23.070 --> 00:09:25.230 quick experiment fails, how do we roll it back 00:09:25.230 --> 00:09:27.850 cleanly without causing more disruption? This 00:09:27.850 --> 00:09:31.070 is action with constraint. It honors velocity 00:09:31.070 --> 00:09:34.450 while actively mitigating risk. Okay, I agree 00:09:34.450 --> 00:09:36.649 completely. The discipline is the crux here. 00:09:36.830 --> 00:09:39.389 And those guardrails you mentioned are an essential 00:09:39.389 --> 00:09:42.009 part of the Ship It Now toolkit, if you're going 00:09:42.009 --> 00:09:45.789 to use it. But we must add another layer of complexity, 00:09:46.250 --> 00:09:48.289 especially when dealing with global or hybrid 00:09:48.289 --> 00:09:51.309 professional groups. We need to consider global 00:09:51.309 --> 00:09:54.809 etiquette. In many high -context cultures, where 00:09:54.809 --> 00:09:57.190 discussion itself is integral to relationship 00:09:57.190 --> 00:09:59.970 building and showing respect, just parking an 00:09:59.970 --> 00:10:02.830 idea, however efficiently, can easily be perceived 00:10:02.830 --> 00:10:05.950 as a brush -off, or even a subtle disrespect. 00:10:06.409 --> 00:10:08.889 If we must park an idea on these settings, the 00:10:08.889 --> 00:10:11.769 etiquette demands mitigation, clear mitigation. 00:10:12.129 --> 00:10:14.950 This means providing explicit appreciation, publicly 00:10:14.950 --> 00:10:17.450 recording the item with the owner, and those 00:10:17.450 --> 00:10:19.730 clear next steps we talked about earlier, title 00:10:19.730 --> 00:10:22.710 owner next step, and setting a definite concrete 00:10:22.710 --> 00:10:25.789 revisit date. If the process feels opaque, it 00:10:25.789 --> 00:10:28.850 feels dismissive. So maybe we need a practical 00:10:28.850 --> 00:10:33.289 playbook rule. If the idea genuinely accelerates 00:10:33.289 --> 00:10:36.559 the agenda's core outcome, OK, maybe ship it, 00:10:36.559 --> 00:10:39.360 but with strong guardrails. If it threatens the 00:10:39.360 --> 00:10:42.179 core outcome, you park it, but with absolute 00:10:42.179 --> 00:10:44.299 transparency and commitment to revisit. That 00:10:44.299 --> 00:10:47.320 cultural point is powerful. I agree. If parking 00:10:47.320 --> 00:10:50.000 feels like dismissal, it absolutely destroys 00:10:50.000 --> 00:10:53.100 future contribution. But the counter to that 00:10:53.100 --> 00:10:55.519 cultural concern could be that some high -context 00:10:55.519 --> 00:10:58.840 cultures might actually value immediate, tangible 00:10:58.840 --> 00:11:01.100 outcomes like the quick launch of a small fix 00:11:01.100 --> 00:11:04.470 over a long, deferred process. Tangible action 00:11:04.470 --> 00:11:07.129 builds trust immediately, right? Whereas deferred 00:11:07.129 --> 00:11:09.769 commitment relies on a high degree of pre -existing 00:11:09.769 --> 00:11:12.350 organizational trust that, let's face it, often 00:11:12.350 --> 00:11:16.350 isn't there. So, to summarize my position, disciplined 00:11:16.350 --> 00:11:19.210 parking, when done right with proper owners and 00:11:19.210 --> 00:11:21.850 scheduled dates, is fundamentally focused with 00:11:21.850 --> 00:11:24.570 memory. It represents, I believe, the highest 00:11:24.570 --> 00:11:26.490 professional etiquette for groups working under 00:11:26.490 --> 00:11:29.429 collective cognitive load. It honors both the 00:11:29.429 --> 00:11:31.269 agreed -upon agenda and the team's collective 00:11:31.269 --> 00:11:34.320 attention span. And crucially, it helps prevent 00:11:34.320 --> 00:11:37.059 the rework and the tech debt, those long -term 00:11:37.059 --> 00:11:39.940 costs that inevitably come from dumping half 00:11:39.940 --> 00:11:42.279 -baked pivots into shared systems without a structured 00:11:42.279 --> 00:11:46.299 landing zone. And I maintain that shipping with 00:11:46.299 --> 00:11:49.259 gates and safeguards in place is courage with 00:11:49.259 --> 00:11:52.620 constraint. It's the ultimate etiquette for outcomes, 00:11:53.220 --> 00:11:55.799 honoring both velocity and the needs of the customer 00:11:55.799 --> 00:11:59.519 by prioritizing impact delivered sooner. The 00:11:59.519 --> 00:12:02.360 ultimate failure of professionalism here, I think, 00:12:02.759 --> 00:12:05.519 isn't really the choice between parking or shipping. 00:12:06.080 --> 00:12:09.320 It's the choice of ambiguity saying, later, with 00:12:09.320 --> 00:12:12.440 no owner, no date, no next step, or executing 00:12:12.440 --> 00:12:15.240 now with absolutely no guardrails, no revert 00:12:15.240 --> 00:12:20.200 plan. That's the real danger. Ultimately, I suspect 00:12:20.200 --> 00:12:22.360 the most professional teams, the most effective 00:12:22.360 --> 00:12:25.759 ones, they have to master both approaches. They 00:12:25.759 --> 00:12:28.559 recognize that the choice is contextual. It depends. 00:12:29.100 --> 00:12:31.639 They adjust their default setting based on the 00:12:31.639 --> 00:12:35.220 item at hand. For instance, serious regulatory 00:12:35.220 --> 00:12:37.639 or compliance issues? Those probably should default 00:12:37.639 --> 00:12:40.980 to park and expert review, but a critical customer 00:12:40.980 --> 00:12:43.960 on fire issue that likely has to default to ship 00:12:43.960 --> 00:12:46.559 now, perhaps with immediate post -mortem and 00:12:46.559 --> 00:12:49.559 mitigation planning baked in. Exactly. Clarity 00:12:49.559 --> 00:12:51.960 is the ultimate courtesy, isn't it? We could 00:12:51.960 --> 00:12:54.039 even utilize quick tools like the two -minute 00:12:54.039 --> 00:12:57.019 test. Can two minutes of focused discussion right 00:12:57.019 --> 00:13:00.019 here, right now, decide the go -no -go status, 00:13:00.240 --> 00:13:02.059 the initial scope, and the owner for this new 00:13:02.059 --> 00:13:05.759 idea? If yes, great. Decide now. If not, okay, 00:13:05.940 --> 00:13:08.159 park it, but immediately apply those necessary 00:13:08.159 --> 00:13:10.820 professional fields we discussed, title, why 00:13:10.820 --> 00:13:13.419 it matters, owner, and next step, ensuring it 00:13:13.419 --> 00:13:16.379 moves into a living, trusted system. The true 00:13:16.379 --> 00:13:19.080 professional standard lies in that explicit communication 00:13:19.080 --> 00:13:22.299 about why, who, when, and how the idea will be 00:13:22.299 --> 00:13:24.799 handled, whichever path is chosen in that moment.