We scan new podcasts and send you the top 5 insights daily.
Oles still puts similar specialists together so they learn fast and carry context, but assigns cross-functional teams to a KPI, output or project. She worries less about org lines and more about whether people are coachable and what work they are moving forward, especially on complex efforts like Dreamforce.
Giving marketing a goal for one stage of the pipeline and sales a goal for another creates friction. Instead, hold all teams accountable for the same end goal (e.g., total pipeline generated), while clarifying how their specific inputs contribute to that outcome.
Handing off initiatives across functional silos is typically where product innovation falters. Keeping a cross-functional team—spanning sales, marketing, engineering, and development—intact throughout the entire project lifecycle ensures alignment and delivers stronger product results.
AI tools are dissolving the traditional boundaries between product, design, and engineering. This shift makes functional silos archaic. The future of organizational design is smaller, cross-functional groups that own a customer problem end-to-end, rather than being grouped by capability like "the engineering team."
The most effective teams are formed by finding the right mix of complementary skills and personalities, rather than filling predefined role slots. An "unstoppable" team's composition should be fluid; it might not even include a formal PM if the chemistry between engineering and design is right.
Apply the logic of agile "flash teams" to your stable team by treating its boundaries as porous. Adopting an "experts everywhere, all the time" mindset encourages you to constantly look for and pull in expertise from anywhere—inside or outside the organization—to break down team silos and accelerate problem-solving.
Instead of fixed roles, initiatives are led by a "captain" whose expertise is most vital for success. An engineer captains an architectural refactor; a designer captains an interaction-heavy feature. This ensures the right leadership for every unique challenge.
AI development makes identifying the right use case and wrangling data the new bottlenecks, not coding. This flattens traditional hierarchies. The most effective teams are integrated 'tiger teams' where UX designers manage RAG files and developers talk to customers, valuing adaptability over rigid job descriptions.
To maintain speed in a large organization, ignore the formal org chart. Instead, structure work around small, empowered 'work chart' teams (squads). Give them a clear DRI, full context, agency, and a direct 24-hour escalation path to leadership to remove blockers.
To move quickly without sacrificing craft, organizations should assemble lean pods featuring one senior strategic lead and a small bench of individual contributors. Removing intermediate management layers preserves context and unblocks teams to ship with speed.
In the AI era, shift from silos like 'Demand Gen' to cross-functional pods focused on outcomes like 'Brand Relationship' or 'Product Delight.' This model, inspired by product development, aligns teams to solve specific customer problems and better integrates AI agents directly into core workflows.