Names vs. The Nothing This is the first site along the tour. In here we have a void. I remember the building that used to stand here, it was painted blue. Passing through it, you can imagine how us, as ghosts – should the building be standing here – would have to actually be invisible to pass through these walls and now it’s the reverse. The building is the ghost and we’re passing through these walls. Graham Coreil-Allen & Roman Mars, 99% Invisible 99percentinvisible.org New Public SitesLocal Code: 3,659 Proposals About Data, Design & The Nature of Cities emptinessnamescities
99% Invisible A Podcast by Roman Mars & Kurt Kohlstedt 99percentinvisible.org The Worst Video Game EverSome Other Sign that People Do Not Totally Regret LifeThe Help-Yourself CityLawn OrderNames vs. The Nothing+7 More designunderstanding
The 99% Invisible City A Book by Roman Mars & Kurt Kohlstedt 99percentinvisible.org urbanismcitiesdesignarchitecturedetails
The Worst Video Game Ever A Podcast from 99% Invisible by Roman Mars & Howard Scott Warshaw 99percentinvisible.org Disorientation
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. Marty Cagan, Product vs. Feature Teams svpg.com What went wrong? teamwork