Working definition
Team Player is an external appointment that creates engagement you cannot generate alone — a conscious constraint you install on purpose, not an unconscious dependence on other people.
How it works
Solo systems stall when the only accountability is internal negotiation. Booking a person into the calendar moves complexity out of the evening scatter and into a fixed slot (Tesler’s Law · Parkinson’s Law). The appointment is the plane: it leaves. That is Be Your Real Boss — you author the constraint — not people-pleasing or waiting to “feel ready.”
Score the system by friction versus efficiency (Efficiency vs Effectivity), not by moral purity about needing others. A configured AI journal can roll for months; a Team Player still closes the loop when the project needs a human witness. Pair with extreme discipline → extreme freedom: the elegance inside discipline is often automation and one hard external date.
Signature
One important project. One external appointment. No new grid — the calendar line is the form. Same family as Friday-before-vacation energy and the plane that does not renegotiate.
Your move this week
Today’s micro-action (24–72 hours): Book one Team Player — an external appointment on one important project. Write the project name and the time; do not add a second accountability tool.