Work Culture & Management
Overview
The work-culture notes are less about abstract leadership theory and more about practical operating behavior: how teams communicate, how priorities are made visible, how managers coordinate without creating bottlenecks, and how individuals behave effectively inside modern knowledge-work environments.
A recurring theme is that healthy work culture is not just about friendliness or morale. It is built through systems: clear goals, visible work, disciplined communication, useful feedback loops, and a bias toward shared understanding.
Core Areas
Agile Team Operating Model
A major thread in the source material is Agile as a day-to-day way of working rather than just a methodology label. Teams are expected to deliver incrementally, raise blockers early, and keep updates concise enough that everyone can understand dependencies and impact.
This includes practical behaviors such as:
- preparing short, structured status updates
- avoiding unnecessary detail in standups
- framing updates in terms of impact on other people
- surfacing delays together with proposed solutions
Goal Systems and Alignment
The strongest explicit management framework in the folder is OKR. The notes emphasize that objectives provide direction while key results provide measurable proof of progress. Good culture depends on people knowing not only what they are doing, but what success means and why the work matters.
Measurement is double-edged, though. Measurement Dysfunction is the caution that badly chosen metrics get gamed — “what gets measured gets managed” is both misattributed to Drucker and known-flawed since 1956. Developer Productivity Measurement shows the constructive counter-pattern: start from goals (Goals-Signals-Metrics) and measure experience rather than individual performance.
Communication and Upward Management
Several notes focus on communication quality:
- clarify task expectations before starting work
- when reporting problems, bring possible solutions instead of only obstacles
- communicate results clearly and early
- summarize learnings into reusable methods or SOPs
The upward-management notes frame this as reducing ambiguity and building trust with leaders through clarity, ownership, and solution-oriented communication.
Management Transparency
The “manage like an engineer” note introduces a particularly strong pattern: use the same visible, durable systems for management work that engineering teams use for software work. Issues, boards, markdown docs, and review flows create:
This also connects directly to Stakeholder Management and Role Clarity, because transparent work depends on people knowing who owns a decision, who contributes input, and who needs visibility.
- clearer visibility into what managers are doing
- better institutional memory
- more asynchronous collaboration
- less dependence on private chat and hidden context
This theme aligns strongly with the rest of the folder: healthy culture is easier when work has shared artifacts, not just private conversations.
People, Feedback, and Resilience
The folder also points toward softer but still operational themes:
- coaching
- feedback quality
- resilience under pressure (Resilience)
- mentorship
- awareness of microaggressions and inclusive behavior
These are not separate from execution. They shape whether teams can stay effective, honest, and collaborative over time, and they are explored in more detail in Coaching and Manager Development and Communication and Feedback at Work.
Values and Value Distribution (Anker)
From a 小林说 interview with Stephan of Anker — a case where stated values were revised because they weren’t producing the intended behavior.
“Experience is not the most important thing. What matters is the person, and their values.” — 经验不是最重要的，重要的是人，是价值观
The slogan changes, and why:
| Before | After |
|---|---|
| 讲道理 (be reasonable) | 第一性 (first principles) |
| 求卓越 (pursue excellence) | 求极致 (pursue the extreme) |
| 共成长 (grow together) | unchanged |
“Pursue excellence” was decomposed into three levels: (1) beat yesterday’s self, (2) beat your peers, (3) beat the consumer’s fundamental need. In practice teams optimized levels 1 and 2 and rarely reached level 3 — so the value was rewritten to name only level 3 outright. A useful pattern: when a value permits a comfortable partial interpretation, teams will take it.
第一性 / first principles as an operating instruction: strip away surface facts → return to basic principles → grab the decisive breakthrough point.
Retaining creators — splitting the money. Money goes to value creators first, at a 7:3 split with creators taking 70%, measured against surplus value (what employees take plus what shareholders take).
The surplus-value ratio is used as a company-tier signal: Apple ~30% (first-tier), Anker ~19% (second-tier). Higher ratio = more value flowing to creators.
Mechanisms: a bonus pool, plus a per-new-domain option pool that the company buys back — an idea borrowed from how real-estate projects are financed per-project rather than per-firm.
Where opportunity lives (the product-evolution ladder): non-adjustable (a fixed chair) → adjustable (an ergonomic chair) → self-adjusting (a massage chair that adapts). Each rung is a new product category rather than an improvement of the last.
Recurring Principles
- make work visible
- write things down
- align on outcomes, not just tasks
- communicate clearly and early
- bring proposed solutions with problems
- keep feedback loops short
- treat culture as a system of habits, not a slogan
Relationships
- Agile — core delivery mindset in the source material
- OKR — goal-setting and alignment framework used by teams and managers
- Stakeholder Management and Role Clarity — role clarity and responsibility systems inside collaborative work
- Coaching and Manager Development — leadership and team-development behaviors for managers
- Communication and Feedback at Work — practical communication layer for feedback, listening, and escalation
- Career Development — many of these habits also function as career-scaling behaviors
- Learning Methods & Growth — reflection, iteration, and feedback connect workplace practice to personal growth
- System Thinking — useful lens for treating culture and organizations as systems rather than isolated incidents
- Widget Factory vs Film Crew — two opposed operating cultures (Theory X vs Y) and how they shape hierarchy, pay, and talent
- Engineering Leadership (CTO Checklist) — the full People/Processes/Technology responsibility surface of a “Head Of” role
- Talent Retention — the salary-compression cycle that hollows out an engineering org while the business still runs
- Respect Over Diversity — why a demographic headcount is not a culture, and subjective review criteria are the real failure
References
- _Work Culture
- Anker Interview from 小林说
- OKR
- Management Like an Engineer
- 向上管理
- How to work 如何有效沟通