Tags
Writing, research, projects, and photos around “Leadership”.
Condensing the judgments that have recurred over the past few years in management, collaboration, and decision-making into a single master summary told just once: judgment, boundaries, alignment, context, closed loop, resources, team, and retrospective — each pointing to one expanded article.
A framework paper that advances structured thinking from the generic expression of "conclusion first, mutually exclusive and collectively exhaustive" into a four-stage problem-location method — Structure → Surface connections → Infer root problem → Find solution — with the causal, duality, dialectical, position, and interest lenses at its core, offering a testable training protocol and its boundaries of use.
Read summaryA farewell, reflection, and word of thanks at the end of an eight-and-a-half-year career journey.
Recruiting branding is not about polishing a job posting; it is about making the right people believe: the work is worth doing, the team has a chance to make it happen, and they can push it into reality together with their peers.
An uncompressed question bank: prepare promotion materials, interview answers, and stage reviews item by item across business, technology, team, individual judgment, and organizational capability.
The purpose of developing a team is not to pour experience into everyone, but to make judgment, collaboration, and responsibility things that can be practiced, given feedback on, and passed on.
Part of the column “Building Teams” · Chapter 4
Growth paths are not job-level checklists but three expanding responsibilities: completing tasks, owning problems, and enabling others to do important work.
Part of the column “Building Teams” · Chapter 5
When an existing bench has failed or you need to start over, rebuild responsibility, standards, and development mechanisms first — not just redraw a division-of-labor chart.
Part of the column “Building Teams” · Chapter 2
Time management isn't about packing your calendar full; it's about clarifying your commitments—and what you won't do right now—based on role, value, and opportunity cost.
Managers don't need to review every line of code, but if they drift away from front-line detail they lose the ability to judge risk, cost, and what is really blocking the team; the point is to build sampling-based understanding, not micro-control.
Frontline management is not about doing a bit more work for the team; it is about continuously producing better judgment, predictable delivery, and a collaboration system that can repair itself.
Part of the column “Building Teams” · Chapter 1
A team is not simply the sum of its headcount and abilities. Real growth means forming, over time, more reliable collaboration, transferable experience, and the capacity to keep solving problems when circumstances change.
Part of the column “Building Teams” · Chapter 3
Recruiting is not just about filling a vacancy; it is about continuously clarifying what the team needs and can offer, and calibrating judgment with every choice.
Part of the column “Recruiting & Professional Relationships” · Chapter 1
Responsibility isn't mindless overtime or mindlessly taking on work. This set of questions makes clear 'who decides, who executes, when to escalate, and where accountability ends.'
Part of the column “One-on-One Conversations” · Chapter 5
A mentor's value lies not in planning everything for the new hire, but in jointly building goals, feedback, and a rhythm of gradually stepping back; a workable 90-day plan makes this traceable.
Part of the column “Building Teams” · Chapter 6