# Organizational Published articles for Organizational. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response DevFeed: [How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response]() Original publisher: [Read original article]() Author: Vanessa Huerta Granda Published: 2026-09-17T09:30:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [incident](), [Incident response]() Tags: [devops](), [incident](), [incident-response](), [infoq](), [limits](), [organizational](), [outages](), [presentation](), [qcon-san-francisco-2026](), [qcon-software-development-conference](), [real-world](), [stream-incidents](), [structured](), [system](), [transcripts]() ### AI overview Vanessa Huerta Granda discusses how prolonged incidents reveal gaps between planned work and work as performed. Drawing on real-world scenarios, the presentation examines organizational fragility, human limits, system interdependencies, and the need for structured, humane, cross-functional incident response. ### Source excerpt Vanessa Huerta Granda explains how marathon incidents expose the gap between work as imagined and work as done. Drawing from real-world scenarios, she shares how complex outages reveal organizational fragility, human limits, and system interdependencies--and why incident response requires structured endurance, humane rotations, and holistic cross-functional coordination. By Vanessa Huerta Granda ## Executive Director Search Extended to September 22 DevFeed: [Executive Director Search Extended to September 22]() Original publisher: [Read original article]() Author: Jeff Triplett and the DSF Board Published: 2026-09-16T12:50:40Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [Open Source](), [Job]() Tags: [2026](), [communication](), [community](), [django](), [framework](), [fundraising](), [job](), [leadership](), [open-source](), [organizational](), [python](), [relationships]() ### AI overview The Django Software Foundation has extended applications for its first Executive Director through September 22, 2026, anywhere on Earth. The role focuses on fundraising, partnerships, operations, and supporting the Django community. ### Source excerpt We are extending the search for the Django Software Foundation's first Executive Director. Applications now close at the end of Tuesday, September 22, 2026, anywhere on Earth (AoE). As long as it is still September 22 somewhere, your application counts. We are happy with the applications we received. We also knew several people had applications in progress, and it took a while for word about the role to reach everyone it should have. Giving people a little more time felt like the fairest option. If you were most of the way there, you have until Tuesday. If you have already applied, this does not slow anything down for you. We are reviewing applications as they come in, and we will reach out to candidates and schedule interviews on the same timeline we planned. The Executive Director will play a central role in helping the DSF grow its capacity and build a sustainable future for the Django project and its community. That includes leading fundraising and partnerships, supporting the Foundation's operations and programs, and working closely with the board, staff, volunteers, and the wider Django community. We are looking for an experienced nonprofit leader who is comfortable taking on a broad role and building things as they go. Fundraising is central to this job. We need someone who is at ease sitting down with companies, making the case for Django, and connecting what the DSF does to what those organizations care about. Much of the Foundation's future depends on growing those relationships and turning them into steady support. You don't need to be a Django or Python expert, and you don't need prior involvement in the Django community. Experience with open source or other community-driven organizations is welcome, but we are primarily looking for someone with strong fundraising instincts, plus leadership, communication, relationship-building, and organizational skills. Could that person be you? If you have been waiting for the right opportunity to step forward, we enc ## The Engineering Manager's role is under attack (again) DevFeed: [The Engineering Manager's role is under attack (again)]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-09-01T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Development](), [Artificial Intelligence](), [Large Language Model](), [Software](), [Meta]() Tags: [agents](), [ai](), [engineering-manager](), [llms](), [meta](), [organizational](), [processes](), [software]() ### AI overview A commentary on the erosion of the Engineering Manager role as companies flatten organizations and expect managers to manage larger teams while also shipping code. It argues that AI-related efficiency claims may reinforce a cycle of reduced management capacity and value. ### Source excerpt The erosion of the EM role ## Using Data Contracts to Coordinate Data Evolution at Enterprise Scale DevFeed: [Using Data Contracts to Coordinate Data Evolution at Enterprise Scale]() Original publisher: [Read original article]() Author: Keerthipriyan Published: 2026-08-25T20:22:17Z Content type: article Language: en Sources: [Walmart Global Tech]() Topics: [data-platforms](), [Data Quality](), [DataOps](), [systems]() Tags: [architecture](), [data](), [data-engineering](), [data-governance](), [data-platforms](), [data-quality](), [data-science](), [enterprise](), [organizational](), [pipeline](), [schema](), [software-engineering](), [teams](), [technology]() ### AI overview The article explains how data contracts help large enterprises coordinate changes across independently evolving data teams and downstream consumers. It argues that schema validation alone cannot identify ownership, downstream impact, or migration responsibilities, and presents data contracts as machine-enforceable coordination agreements. ### Source excerpt Coauthored by Satyajeet Coordinating Data Evolution at Enterprise Scale When you operate data platforms on a global enterprise scale, hundreds of engineering teams ship improvements every week, each moving independently to deliver value at the pace of the business demands. This velocity is a competitive advantage. The challenge: How do you enable hundreds of teams to evolve their data products independently while maintaining reliability for thousands of downstream consumers? Traditional coordination methods (messages, wiki updates, shared spreadsheets) work at small scale but break at Walmart scale. A source team ships an enhancement, perfectly valid within their domain, but that change ripples through fifteen downstream pipelines owned by different teams with different release schedules. Without a formal coordination mechanism, you discover the impact after it reaches production. The gap isn't technical debt or fragile systems. It's the absence of machine-enforceable agreements that scale with organizational complexity. Data contracts solve this: enabling teams to move fast independently while maintaining coordinated reliability across organizational boundaries. Here's the architecture we built. Why Schema Validation Alone Isn't Enough When data quality issues surface in production, the first instinct is often added to more schema validation. If a field is missing or has the wrong type, the pipeline catches it. This works for many data quality problems, but not all of them. Consider a scenario where a source team enhances their data model by restructuring field names to support new business capabilities. The schema still validates perfectly: every field exists; every type is correct; the data is well formed. But downstream consumers who depend on the original field names now receive empty results. Schema validation checks whether data has the right shape. It tells you that a field is missing. It does not tell you who owns that field, which downstream teams will bre ## What is a Minimum Viable Platform (MVP)? DevFeed: [What is a Minimum Viable Platform (MVP)?]() Original publisher: [Read original article]() Author: Luca Galante Published: 2026-08-21T14:37:28Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [Developer Platform](), [Shared Responsibility Model]() Tags: [engineering](), [evaluation](), [gartner](), [idp](), [internal-developer-platform](), [organizational](), [platform](), [platform-engineering](), [shared-responsibility](), [speed]() ### AI overview This article explains why platform engineering initiatives often fail despite widespread adoption of internal developer platforms. It argues that culture, process, and delivery speed matter more than tooling choices, and recommends starting with a Minimum Viable Platform to build stakeholder support and deliver value quickly. ### Source excerpt Unlock success in platform engineering: Avoid common pitfalls, embrace MVP approach, and win stakeholder support for a transformative platform initiative. ## Univé builds an AI-ready workforce DevFeed: [Univé builds an AI-ready workforce]() Original publisher: [Read original article]() Published: 2026-07-31T07:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [ChatGPT](), [AI Strategy](), [OpenAI](), [Responsibility & Safety](), [responsible-ai](), [Security](), [Security & Privacy](), [Authorization](), [Monitoring](), [Authentication]() Tags: [ai](), [authentication](), [building](), [chatgpt](), [enterprise](), [governance](), [innovation](), [leadership](), [monitoring](), [openai](), [organizational](), [platform](), [privacy](), [responsible-ai](), [scale](), [security](), [security-privacy](), [strategy](), [technology]() ### AI overview Univé describes building an AI-ready workforce by treating AI adoption as an organizational transformation rather than a technology deployment. Using ChatGPT Enterprise within its governance framework, the insurer combined leadership engagement, employee-led innovation, enterprise authentication, permission controls, privacy assessments, security reviews, responsible AI principles, continuous monitoring, and human accountability to support safe experimentation at scale. ### Source excerpt See how Univé built an AI-ready workforce with ChatGPT Enterprise by combining leadership, responsible governance, and employee-led innovation to transform work at scale. ## When is the right time to adopt an IDP? DevFeed: [When is the right time to adopt an IDP?]() Original publisher: [Read original article]() Author: Trevor Garcia Published: 2026-07-30T10:13:18Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Developer experience](), [DevOps](), [sdlc](), [Product Management](), [Tooling]() Tags: [article](), [best-practices](), [developer](), [developer-experience](), [developer-portal](), [devops](), [engineering](), [idp](), [internal-developer-portal](), [management](), [organizational](), [platform](), [platform-engineering](), [sdlc](), [software-development](), [tech-stack](), [tooling](), [tools]() ### AI overview This article explains when organizations should consider adopting an internal developer portal (IDP). It identifies scaling challenges such as operational overhead, cognitive overload, duplicated tools, unclear ownership, and inconsistent tooling. It also describes how DevOps, platform engineering, and product management practices can support an IDP that improves developer experience, standardizes tooling, and consolidates organizational knowledge. ### Source excerpt Organizations have to consider a lot of details before adopting an IDP, and it can be hard to know when is the right time. ## Ethereum Foundation Board Update DevFeed: [Ethereum Foundation Board Update]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2026-07-29T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum]() Tags: [ecosystem](), [ethereum](), [organizational](), [update]() ### AI overview The Ethereum Foundation announces that pcaversaccio (pc) has joined its board for an initial one-year voluntary term. The board oversees the Foundation's vision, high-level strategy, values, security, and compliance. ### Source excerpt We are pleased to share that pcaversaccio (pc) has joined the Ethereum Foundation Board. pc is a long time contributor to the Ethereum ecosystem, a co-founder and lead of SEAL 911, and has been a member of the EF's Silviculture Society, which provides informal counsel to EF aimed at... ## What does a platform product manager do? DevFeed: [What does a platform product manager do?]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T08:14:05Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [Product Management](), [Developer experience]() Tags: [architecture](), [developer-experience](), [developer-platform](), [developers](), [engineering](), [internal-developer-platform](), [management](), [organizational](), [platform](), [platform-engineering](), [platforms](), [product](), [product-management](), [product-strategy](), [strategy](), [technical](), [user-research]() ### AI overview This guide explains the role of a Platform Product Manager (PPM) in driving strategy for an Internal Developer Platform. PPMs connect technical platform capabilities with developer needs through user research, feedback loops, roadmaps, stakeholder management, and outcome metrics. The article distinguishes product thinking from project management and describes how continuous prioritization and clear platform boundaries support adoption. ### Source excerpt Platform Product Managers drive internal developer platform strategy, bridging technical capabilities and developer needs through research, roadmaps, and stakeholder management. ## Five key recommendations for platform teams in 2026 DevFeed: [Five key recommendations for platform teams in 2026]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Artificial Intelligence](), [AI Platforms/Deployment]() Tags: [2026](), [ai](), [complexity](), [engineering](), [leadership](), [organizational](), [platform-engineering](), [platforms]() ### AI overview The article presents five recommendations for platform teams in 2026, based on reported execution gaps in measuring success, developer adoption, proving return on investment, integrating AI, and managing multiple platforms. It emphasizes disciplined execution and treating platform engineering as a product with dedicated leadership. ### Source excerpt Five actionable recommendations for platform teams in 2026 to maximize ROI, drive adoption, integrate AI, and build effective, scalable platform strategies ## 3 reasons IT service providers are essential for enterprise platform engineering (now more than ever) DevFeed: [3 reasons IT service providers are essential for enterprise platform engineering (now more than ever)]() Original publisher: [Read original article]() Author: Karolina Semiuk Published: 2026-07-23T05:40:01Z Content type: opinion Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Architecture & Design](), [Security]() Tags: [cognitive-load](), [development](), [engineering](), [enterprise](), [infrastructure](), [learning](), [management](), [operations](), [organizational](), [partners](), [platform](), [platform-engineering](), [scale](), [shared-responsibility](), [tools]() ### AI overview This article argues that IT service providers are increasingly essential to enterprise platform engineering. It identifies cultural transformation, specialized talent shortages, and the need to keep pace with rapidly changing practices as challenges that enterprises often cannot address alone. Providers contribute external perspective, change-management frameworks, and experience from multiple implementations. ### Source excerpt Discover why IT service providers are vital for enterprise platform engineering success: cultural change, talent shortages, and adapting to rapid technical evolution. ## Why enterprises fail at platform engineering: Project vs Product mindset DevFeed: [Why enterprises fail at platform engineering: Project vs Product mindset]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: opinion Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [DevOps](), [Developer Platform]() Tags: [cognitive-load](), [devops](), [engineering](), [idp](), [internal-developer-platform](), [leadership](), [organizational](), [platform-engineering](), [scale](), [workflows]() ### AI overview The article argues that enterprises succeed with platform engineering when they treat the Internal Developer Platform as a continuously evolving internal product rather than a finite engineering project. A product-led approach investigates developers' problems, supports adoption, aligns stakeholders, secures ongoing investment, and uses a Platform Product Manager to connect user needs, technical priorities, and business goals. ### Source excerpt Discover why enterprises struggle with platform engineering and how shifting from a project mindset to a product-led approach drives adoption, alignment, and real developer value ## The biggest challenges platform engineering teams are facing in 2026 DevFeed: [The biggest challenges platform engineering teams are facing in 2026]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Product Management]() Tags: [2026](), [building](), [business-value](), [developer](), [engineering](), [how-to](), [organizational](), [platform](), [platform-engineering](), [report](), [strategy](), [technical]() ### AI overview This article examines the biggest challenges facing platform engineering teams in 2026. Based on the State of Platform Engineering Vol 4 report, it argues that cultural and organizational barriers--especially developer adoption, shared vision, product mindset, and change management--outweigh purely technical difficulties. It recommends launching Minimum Viable Platforms, building adoption through early advocates and a Bottom-Up-Top-Down strategy, securing executive alignment, and measuring outcomes to demonstrate ROI. ### Source excerpt Is your platform engineering initiative struggling? Data shows cultural and organizational barriers, not technical ones, are the biggest hurdle. Learn why developer adoption is the top challenge, how to build an MVP, secure executive buy-in, and measure ROI for platform success based on the State of Platform Engineering Vol 4 report. ## Creating a shared platform vision: How platform leaders align teams DevFeed: [Creating a shared platform vision: How platform leaders align teams]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [internal developer portal]() Tags: [developer-platform](), [idp](), [internal-developer-platform](), [leadership](), [organizational](), [platform](), [platform-engineering](), [strategy]() ### AI overview This article presents a framework for creating a shared vision for an internal developer platform. It explains that platform initiatives often fail because executives, developers, security, and operations teams have different expectations, incentives, and measures of success. Platform leaders must build stakeholder alignment, communicate shared value, and use deliberate strategy to support genuine adoption. ### Source excerpt Framework for aligning executives, developers, and ops on an internal developer platform vision using shared language, metrics, and product-minded roadmaps ## Why installing Argo CD didn't fix your deployments DevFeed: [Why installing Argo CD didn't fix your deployments]() Original publisher: [Read original article]() Author: Koray Oksay Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [GitOps](), [Deployment](), [Git](), [Kubernetes]() Tags: [argo-cd](), [deployment](), [flux](), [git](), [kubernetes](), [organizational](), [production]() ### AI overview The article argues that installing Argo CD or Flux does not by itself make deployments safer, auditable, or self-service. GitOps exposes unresolved organizational questions about production ownership, approval authority, accountability, repository access, and operational responsibility. Successful GitOps adoption therefore depends on organizational design and clearly defined trust boundaries, not only on tooling. ### Source excerpt GitOps tools like Argo CD won't solve underlying organizational issues. This article argues that GitOps is an organizational decision that exposes pre-existing ambiguity around ownership, production responsibility, and trust boundaries. Learn why clear organizational design is the true foundation for GitOps success. ## How NIIT helped Kyndryl certify more than 100 platform engineers DevFeed: [How NIIT helped Kyndryl certify more than 100 platform engineers]() Original publisher: [Read original article]() Author: Karolina Semiuk Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer portal](), [Developer experience](), [Scalability](), [DevOps]() Tags: [best-practices](), [certifications](), [community](), [devops](), [efficiency](), [engineering](), [enterprise](), [organizational](), [platform](), [scalability](), [software-delivery]() ### AI overview The article describes how NIIT helped Kyndryl certify more than 100 platform engineers. It argues that team-scale certification creates shared language, reduces communication problems, standardizes best practices, and strengthens platform engineering capabilities across a distributed enterprise workforce. ### Source excerpt NIIT enabled Kyndryl to certify 100+ platform engineers, fostering shared language and organizational transformation through team-based certification programs ## What enterprises actually want from platform engineering service providers: Beyond tools to transformation DevFeed: [What enterprises actually want from platform engineering service providers: Beyond tools to transformation]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [DevOps](), [Cloud](), [Security]() Tags: [cloud](), [devops](), [engineering](), [organizational](), [partner](), [platform](), [platform-engineering]() ### AI overview Platform engineering initiatives depend more on organizational alignment and cultural change than on selecting particular tools. The article argues that enterprises need service providers who can align stakeholders, establish a shared vision, understand organizational workflows, and translate platform engineering's value across security, compliance, development, and executive groups. Trust and contextual understanding may matter more to buyers than technical differentiation. ### Source excerpt Platform engineering success hinges on organizational alignment and cultural shift, not just tools. Discover what enterprises actually prioritize in service providers: from trust and workflow understanding to context-specific adaptation and stakeholder translation to win big in the $50B market. ## How Wix Built a Code Migration Platform to Automate Cross-Team Repository Changes DevFeed: [How Wix Built a Code Migration Platform to Automate Cross-Team Repository Changes]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-07-22T14:10:18Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [migration](), [Code]() Tags: [automatic](), [code](), [developer](), [engineering](), [infrastructure](), [migration](), [organizational](), [platform](), [process](), [projects](), [scale](), [team]() ### AI overview Wix describes building a Code Migration Platform to reduce the coordination burden of large-scale code migrations. The platform is intended to identify affected repositories, apply changes automatically, and track migration work centrally. The article says Wix initiates 50 migrations annually, affects hundreds of repositories per migration, touches 6,000 repositories each year, and spends 25% of organizational developer time on migrations. ### Source excerpt No one wakes up excited to do a code migration. Deprecated libraries, method version upgrades, infra changes - they happen constantly, they affect dozens of teams, and they always arrive at the worst possible moment. A small technical change somehow becomes months of coordination. Slack threads. Priority negotiation. Manual tracking. Reminders. Many google sheets. For years, I managed cross-team projects at Wix, and migrations were always the hardest part. Not because they're technically... ## A Recap of the 2026 Experimentation Conference at Booking.com DevFeed: [A Recap of the 2026 Experimentation Conference at Booking.com]() Original publisher: [Read original article]() Author: Mel JI Mueller Published: 2026-07-16T08:18:03Z Content type: article Language: en Sources: [Booking.com Data Science]() Topics: [experiments](), [decision-making](), [Artificial Intelligence](), [Tooling]() Tags: [2025](), [ai](), [analysis](), [data-science](), [events](), [experimentation](), [organizational](), [parallel](), [recap](), [themes]() ### AI overview A recap of Booking.com's 2026 Experimentation Conference, which brought together more than 150 experimentation practitioners from 49 companies. The article summarizes survey findings, conference themes, and sessions on AI-assisted experimentation, experimentation quality and velocity, and organizational culture. ### Source excerpt By Kevin Anderson, Angelica Goetzen, Jorden Lentze, and Melanie Mueller On May 18, 2026, we hosted the third annual Experimentation Conference at Booking.com on our Amsterdam campus. What started in 2024 as an experiment itself -- would large-scale experimentation practitioners come together to learn from each other? -- has grown into an event which brings together over 150 practitioners from 49 companies which run experiments at scale. About one third of attendees came back a second or third time. The room collectively ran 56,000 experiments per year. It's a unique crowd, and that's exactly the point. The day opened with sharing the results of the survey data we collected from the participating companies on the state of experimentation across the room, revealing some interesting findings: most teams operate a centre of excellence model, roughly a third release over 90% of features through controlled experiments, and the top challenges are scaling, coordination, platform tooling, and culture. These shared experiences helped shape the programme. We had three sessions, grouped by the three conference themes: AI and experimentation: AI-assisted analysis, no-code experimentation Quality / velocity tradeoff: High-quality vs high-speed experimentation Experimentation culture: Build organizational buy-in and data-driven decision-making Each session followed the same format: two talks, then a panel discussion on the same topic. We closed with nine parallel breakout groups for deeper conversation. Below is a recap of the key sessions. Read the recap of 2025 | Read the recap of 2024 Session 1: AI and experimentation The conference started off with the hot topic of AI in experimentation. AI is changing how we experiment and how we support experimenters. How Experimentation Protects Decisions in an AI-Written World -- Marcel Toben Marcel Toben, Head of Engineering at Zalando, opened with a provocation he'd recently heard from software engineers in Berlin: nobody on his team had wr ## CEO Rowan Trollope's organizational announcement to Redis employees DevFeed: [CEO Rowan Trollope's organizational announcement to Redis employees]() Original publisher: [Read original article]() Author: Rowan Trollope Published: 2026-07-15T00:00:00Z Content type: news Language: en Sources: [Redis Blog]() Topics: [Redis](), [genai](), [Artificial Intelligence](), [Software]() Tags: [ai](), [announcement](), [announcements](), [company](), [developers](), [engineering](), [genai](), [organizational](), [workflows]() ### AI overview Redis CEO Rowan Trollope announces an organizational change involving the reduction of approximately 200 roles globally and a realignment of roles, teams, and priorities. The announcement attributes the changes to rapidly evolving customer and developer needs, particularly around GenAI, agents, memory, context, real-time data, and intelligent applications. Redis is also changing its internal workflows, with smaller teams and streamlined processes in Product and Engineering. ### Source excerpt Today, we are announcing an organizational change at Redis, including a reduction of approximately 200 roles globally and a realignment of roles, teams, and priorities across the company. This is a difficult decision because it affects people who hav... ## A return to two-pizza culture DevFeed: [A return to two-pizza culture]() Original publisher: [Read original article]() Author: werner@allthingsdistributed.com (Dr. Werner Vogels) Published: 2026-06-30T14:00:00Z Content type: article Language: en Sources: [All Things Distributed]() Topics: [amazon](), [Code]() Tags: [amazon](), [organizational](), [posts](), [process](), [product](), [writing]() ### AI overview The article revisits Amazon's two-pizza team model, emphasizing small autonomous teams, end-to-end ownership, rapid reversible decisions, experimentation, and customer-focused product development through the Working Backwards process. It also explains how organizational growth, service dependencies, and approval cycles can reduce delivery speed. ### Source excerpt What made the Quick desktop team successful is the same thing that has always produced the best work I've seen at Amazon: a small group of people who trusted each other, owned the problem end-to-end, and acted on their conviction. ## The EF's new structure DevFeed: [The EF's new structure]() Original publisher: [Read original article]() Author: Ethereum Foundation Management Published: 2026-06-23T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Architecture & Design](), [Open Source](), [Security](), [Post-Quantum]() Tags: [ethereum](), [management](), [open-source](), [operations](), [organizational](), [people](), [post-quantum](), [reorganization](), [security](), [structure](), [teams]() ### AI overview The Ethereum Foundation describes a new organizational structure created through a months-long reorganization implementing its Mandate and Treasury Management Policy. The structure includes work clusters covering protocol, access, users, community, institutions, operations, and management, while 54 colleagues leave the foundation. ### Source excerpt Today, the EF is changing shape, concluding a months-long process of reorganization as part of the implementation of the Mandate and the Treasury Management Policy. We come out of this process with the structure, activities, and people necessary for execution on the critical tasks ahead of us, but also... ## De-risking a PagerDuty migration: the objections we hear most, and how to clear them DevFeed: [De-risking a PagerDuty migration: the objections we hear most, and how to clear them]() Original publisher: [Read original article]() Author: Eryn Carman Published: 2026-06-09T14:49:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [migration](), [incident](), [Tooling]() Tags: [engineering](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [infrastructure](), [migration](), [on-call](), [organizational](), [outage](), [platforms](), [post-mortem](), [slack-incident](), [switching](), [technical]() ### AI overview This article explains why migrating from PagerDuty to another on-call platform is primarily an organizational and change-management challenge rather than a technical one. It presents seven common objections, including risk of missed alerts, and discusses how to address them through ownership, consensus-building, testing, and parallel operation before cutover. ### Source excerpt Often, switching on-call platforms isn't a technical challenge but a human one. In this post, we break down the seven objections engineering teams raise most often when considering a PagerDuty migration, and share exactly how to address each one. ## TBM 425: AI and Agency DevFeed: [TBM 425: AI and Agency]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-06-07T23:19:08Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [AI Strategy](), [Artificial Intelligence](), [trust]() Tags: [agent](), [ai](), [ai-adoption](), [leadership](), [organizational](), [trust]() ### AI overview This commentary argues that companies' approaches to AI adoption can undermine employee agency, trust, and dignity. It presents resistance to mandates as a potentially rational response to organizational conditions and argues that employees should be able to learn how AI fits their work on their own terms. ### Source excerpt So you want your team to figure out how to use AI for the benefit of your company? [Next page]()