The article argues that adult mindsets, responsibility, and work standards are hard to reshape, so managers should focus on selecting the right hires early and saying "no" to mismatches rather than hoping slow coaching will change underperforming team members.
The article chronicles DingTalk’s extreme overtime policies—such as the 9127 schedule, “Wangshou” night‑stay rule, and daily‑package pressure—how they harmed employee health and product metrics, triggered a wave of resignations, and forced Alibaba to replace leadership and roll out sweeping reforms within a week.
The article outlines a practical framework for managers to balance delegation and oversight by confirming direction up front, monitoring risks during execution, and avoiding micromanagement, while adapting communication frequency to project urgency and team maturity.
The article examines how Huawei, facing high R&D waste, long cycles and declining margins, looked to IBM’s turnaround under Gerstner and its Integrated Product Development (IPD) framework as a blueprint to build a systematic, efficient R&D system for long‑term products.
This article shares concrete OKR templates, step‑by‑step formulation, implementation, tracking methods, and performance‑linkage advice, offering actionable guidance and visual examples for teams that already have a vision and mission in place.
In this article, a tech leader shares ten concrete practices—from delegating authority to group leads and building personal trust, to handling on‑call releases and protecting subordinates—that have helped him effectively manage a diverse 100‑plus‑person engineering organization.
This guide outlines the mindset, rhythm, and concrete actions senior technology managers need to adopt when transitioning from large enterprises to smaller companies, covering humility, rapid integration, whole‑hearted work attitude, strategic pacing, team building, and systematic process implementation.
This article explains what micromanagement is, why it harms both on‑site and remote teams by reducing trust, morale, and productivity, and offers practical strategies such as delegating responsibility, using project‑management tools, adopting RACI, and embracing asynchronous communication to break the habit.
The article explores whether agile transformation has measurable success criteria, outlines the observable traits of an agile organization, discusses how to evaluate others' transformations meaningfully, and questions if becoming an agile organization is a worthwhile goal for companies.
This article explores how software development leaders can transform their management approach by focusing on clear goals, adaptive leadership, strong culture, continuous improvement, transparency, rapid experimentation, and fun to build autonomous, high‑performing teams.
