1 views collected around this technical thread.
The article analyses why many organizations stall during DevOps adoption, explains the underlying causes, discusses metric design and second‑order changes, and proposes organizational and technical strategies to cross the gap and achieve sustainable continuous delivery.
This article examines two common organizational models—vertical and hierarchical division—detailing their structures, operating modes, advantages, drawbacks, and how they influence employee roles, career paths, and overall company performance in the IT industry.
The article explains why agile transformations often fail when teams focus only on isolated Scrum practices, and proposes that true improvement requires synchronizing the process chain, organizational structure chain, and tool chain to achieve smoother end‑to‑end business delivery.
The article explains enterprise business architecture (EBA) as the bridge between business models and strategy, outlines what EBA is not, describes its four dimensions—personnel, finance, organization, and process—lists key influencing factors, and shows how EBA fits within the broader enterprise architecture context.
The article discusses how technical leaders can break the vicious cycle of low quality, bugs, delays, and overtime by focusing on proper talent placement, clear organizational structures, well‑defined mechanisms like DRI, and systematic processes that improve collaboration, visibility, and overall team efficiency.
The article explains Amazon’s Two‑Pizza team model, emphasizing its core principles of autonomy, responsibility and entrepreneurial spirit, detailing team composition, management practices such as mission‑driven press releases and fitness‑function metrics, and evaluating its advantages and limitations for scaling innovation.
The article recounts a senior technology leader’s journey from early PHP/MySQL work to senior CTO roles at Ant Group and Alibaba, arguing that a CTO must be an executor who aligns business goals with evolving distributed, cloud‑native architectures, outlines three leadership stages, key responsibilities, and offers a Z‑shaped career roadmap for future CTOs.
This article explains business architecture as the bridge between business models and strategy, defines Enterprise Business Architecture (EBA), outlines its four dimensions—people, finance, process, and organization—examines key influencing factors, and describes how it fits within the broader enterprise architecture context.
The article explains how a company can achieve a process‑oriented organization by defining business flow, aligning processes, leveraging IT to solidify data handling, integrating quality standards, and establishing continuous operations, emphasizing the need for clear concepts and roles across the enterprise.
The article examines Spotify’s famed agile “Squad” model, explains why it has not lived up to the hype, and extracts four key lessons—matrix management flaws, excessive focus on autonomy, missing collaboration skills, and the myth‑driven structure—that can help other organizations avoid similar pitfalls.
The talk explains how OKR and Agile, when combined with system thinking and thoughtful organizational design, create iterative, value‑driven processes that align teams across hierarchical layers, adapt to complexity, and transform mission and vision into concrete actions for greater efficiency.
This article examines the evolution of the mid‑platform concept in Chinese tech giants, outlines how companies like Tencent, Baidu, Xiaomi, Didi, JD, NetEase, Yonyou and Zhihu implement and differentiate front‑end, back‑end, and mid‑platform layers, categorizes platform types, and discusses common challenges and organizational pitfalls.
This article explains the concept of a mid‑platform system, its origins, classification into business, technical, data, and organizational types, its lifecycle, and practical guidance on adopting a mid‑platform strategy for companies of any size.
The article analyzes why many DevOps teams devolve into tool‑chain or pipeline roles, examines executor and organizational factors, presents a six‑role DevOps team model linked to the Six Thinking Hats, shares community viewpoints on role prioritization, and concludes that DevOps structures must be tailored to solve concrete business problems rather than follow a fixed standard.
The article explains how organizations can increase adaptability by decentralizing decision authority across microservice components, outlines key decision areas to empower, and offers practical guidance for balancing speed, safety, and governance in modern software development.
Spotify scales agile across dozens of teams by organizing work into autonomous squads, grouping related squads into tribes, and fostering cross‑functional knowledge sharing through chapters and guilds, while using lightweight surveys, hack days, and system‑owner roles to maintain alignment, quality, and rapid delivery.
This article details Ctrip's four‑year journey of using the OK system and OKR framework to create agile OK teams, drive high‑efficiency operations, implement entrepreneurial incentive mechanisms, and cultivate talent through the Huangpu training camp, ultimately reshaping corporate culture and sustaining rapid growth.
This article describes how Ctrip’s Train Ticket SBU introduced the OK organizational model and OKR goal‑setting framework, along with a performance‑based “投名状” incentive and the Huangpu training camp, to maintain agility, drive growth, and foster an entrepreneurial culture within a rapidly scaling R&D organization.
In a Shanghai round‑table, Ctrip co‑founder Liang Jianzhang explained how large enterprises can boost innovation by decentralizing structures, prioritizing market share over short‑term profit, implementing entrepreneurial incentive schemes, removing coordination bottlenecks, and encouraging talent mobility.