Let’s buy a car using the public project process!
summary
Uses the public procurement steps: gather insight, define requirements, evaluate offers, and shows concrete failure modes — vague requirements force selection by price and invite bikes and scooters into the tender, overly specific expert suggestions (a Tesla‑only “car wash mode”) disqualify all but one vendor, and “buy an engine and build a car” proposals hide longterm maintenance costs. Compares off‑the‑shelf cars versus custom builds, counts extra maintenance and vendor lock‑in, and ends with choosing existing public transport.
AI-written summary · about
chapters (13)
- 0:00Public project process
- 1:05Three key steps to start
- 2:09Stakeholder insights
- 3:33Basic car requirements
- 4:17Evaluating public tenders
- 5:41Expert help for domain
- 6:49Refining with expert input
- 8:16Comparing car options
- 9:18Biases in expert advice
- 10:23Custom vs off-the-shelf
- 11:50Why custom in software
- 12:33Maintenance for custom features
- 13:16Do we need a car?
related talks
25mRedesigning a Category: Einride’s Take On Transportation
19mChoosing tech for the enterprise, like you work on The Enterprise
30mBuild vs. Buy - a strategic decision for systems and people
43mDDD for Mergers and Acquisitions
43mPanel: The Platform Rock-Paper-Scissors: Build, Adopt, Buy
10mdigital.auto
23mFrom Auto Parts Manufacturer to Productized Cloud Service at a Large Automotive Supplier
20mDriving Intelligence: The Software Shift Shaping Tomorrow’s Cars