The Product Model and Org Design 5 minutes read.
Re-orgs and org structures are generally considered adequate because they use authority to resolve everything. It can be effective yet highly fragile. They often push us to believe that with the right structure, we will solve talent (who we work with), maturity (how we work together), and execution (what we deliver) automagically. It's easier to exclude org structure types as a clear misfit for the business needs. Once you have cleared that out, choose something that makes sense and leverage your advantages. "For example, if your business calls for a portfolio of loosely related products, each pursuing their own product vision and strategy, then it’s likely that the GM model will be the natural fit. But if the business depends on a tightly integrated, holistic product experience, then the functional model is likely best suited. The main reason the hybrid model is so popular is that many companies do have a portfolio of loosely related products, yet they need the leverage and efficiencies provided by a common platform. Beyond these fairly straightforward heuristics, I often explain to company leaders that it’s tempting to think that a reorganization will fix their company’s issues, but in most cases, it’s simply rearranging the deck chairs on the Titanic."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
How to Design Teams That Don't Suck (podcast) 38 minutes read.
"Trust emerges from a team that is operating well, not the other way around. [...] The bond between people is less important than the bond around the mission. Mission cohesion matter more than social cohesion." -- Adam Grant will make you think about team design (vs. team dynamics) with shared experiences and purpose, working tightly together for a shared goal.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
From Wait to Great: Leveraging LLMs to Boost Aleph’s Organizational Velocity 7 minutes read.
"Most organizations, whether they realize it or not, are often stuck in wait states — periods where progress stalls due to delayed decisions or inaccessible information. These wait states can be costly, leading to missed opportunities and diminished organizational momentum." -- This is a simple yet so powerful insight. Can you map out and reduce wait times? Aleph's approach is creating a clear tradeoff between speed and privacy. This implementation won't work for everyone, yet everyone should think about wait times.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.