grids
Typographic grid
Off the Grid...and Back Again?
An Article by Geoff BoeingMy article “Off the Grid… and Back Again? The Recent Evolution of American Street Network Planning and Design” has been published by the Journal of the American Planning Association and won the 2020 Stough-Johansson Springer Award for best paper. It identifies recent nationwide trends in American street network design, measuring how urban planners abandoned the grid and embraced sprawl over the 20th century, but since 2000 these trends have rebounded, shifting back toward historical design patterns.
Urban Street Network Orientation
An Article by Geoff BoeingThis study measures the entropy (or disordered-ness) of street bearings in each street network, along with each city’s typical street segment length, average circuity, average node degree, and the network’s proportions of four-way intersections and dead-ends. It also develops a new indicator of orientation-order that quantifies how a city’s street network follows the geometric ordering logic of a single grid. These indicators, taken in concert, reveal the extent and nuance of the grid.
Product vs. Feature Teams
This article is certain to upset many people.
Empowered product teams
When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
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.
What went wrong?
If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong.
Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question.
And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question.