Culture
Finding Collective Ownership of the Codebase 3 minutes read.
Leverage Britton Broderick's insights when thinking of your team's principles (e.g. onboarding) and playbooks (e.g. planning, on-call, retrospectives): "Teams with shared understanding and patterns have the foundation for higher velocity. What norms has your team established around shipping? What’s the process for creating new norms and updating old ones? [...] Software engineering is a social activity, not an individual activity. Enabling that social element is key."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
In the Absence of an Accompanying Goal, a System Is Meaningless 3 minutes read.
While it may look intuitive or even obvious, we often focus more (or too much) on the system (process) than the desired outcome. Defining the expected result ("Definition of Done") clearly in a way that leaves very little room for mistakes or misunderstanding is often pushed to the end. We mix progress with tangible deliverables, and celebrate busyness as if it's useful to the business.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Mandate Levels 7 minutes read.
John Cutler is one of my favorite product thinkers (and org thinkers). He takes deep concepts such as Agency and translates them into simpler terms we can observe and sometimes even measure (roughly).
Read it later via
Instapaper.
Share
it via
Twitter
or
email.