The Director's Notebook: Building a System That Survives the Season

Every performance director has a plan in April. Almost none of them survive until October unchanged. That is not a failure of planning. That is the job.

The hardest call I make each year is not about sets and reps. It is about building a performance system agile enough to handle three things that never stop moving: what the coaching staff wants, what the athlete feels, and what the athlete actually produces. All of it inside a schedule that does not care about any of your plans. And underneath all of that, a harder question: who owns what when the department grows faster than its governance?

Start With the North Star

Before any system gets built, you need a single organizing principle that every daily decision can be checked against. Mine is simple: maximize player availability, performance, and career longevity through an integrated system aligned to the demands of the season. In that order.

Availability is the primary outcome. If they are not available, nothing else matters. Performance is the standard of that availability. If they are available but not prepared, we failed the standard. Every programming decision, every load adjustment, every conversation with the coaching staff has to answer two questions: does this improve availability, and does this support performance when it matters most?

This sounds obvious. It is not. Most departments optimize for what is measurable in the weight room rather than what wins in October. The North Star forces you to ask whether today’s work serves the end of the season or just today’s session.

The Three Competing Demands

In professional basketball, you answer to more than the athlete in front of you. The coaching staff has needs that shift by the month. In training camp, they want you to build the engine. By midseason, they want fresh legs. In a playoff push, they want whatever keeps the rotation upright. None of these are wrong. All of them change what you can do in the weight room that week.

Then there is the athlete. What she tells you she feels and what the data says she produced are two different inputs, and you need both. I use a simple four domain daily check: stiffness, heaviness, irritability, and tiredness. Each one points to a different type of fatigue and a different intervention. An athlete who feels terrible but jumps well is in a different place than one who feels great and cannot get off the floor. The subjective report tells you about readiness. The objective output tells you about capacity. A good system listens to both and knows which one to trust on a given day.

The mistake young directors make is building a system that only works when all three align. They do not align. Not for six months. Your system has to function when the staff wants one thing, the athlete feels another, and the numbers say a third.

The Schedule Is the Program

People outside professional basketball do not understand the schedule. It is not just games. It is red eye flights, three time zones in five days, back to backs with a morning shootaround you did not plan for, and a roster where half the players arrived from overseas leagues already carrying fatigue you did not create.

You cannot out program a bad schedule. You can only build a system flexible enough to absorb it. That means your training menu needs tiers, not a single prescription. On a good week, you develop. On a brutal travel week, you maintain. On a week where everything falls apart, you keep the athlete healthy and call it a win. All three are the program working as designed.

I stopped writing programs and started writing frameworks years ago. A program says do this on Tuesday. A framework says here is what Tuesday looks like under three different conditions, and here is how you decide which one you are in. The difference sounds subtle. In a six month season, it is everything.

Microdosing: Train Enough to Maintain, Not Enough to Interfere

The WNBA season does not allow traditional training models. You cannot run a twelve week strength block when you play three games a week for six months. So the question becomes: what is the minimum effective dose that maintains strength, speed, and power without adding fatigue the schedule cannot absorb?

The answer I have landed on is microdosing. Frequent, low volume, high quality exposures to key physical qualities. Fifteen to twenty minutes, a few times a week, low reps with maximum intent. We touch strength often. We do not chase it all at once.

This works because consistency beats intensity in a congested season. Large, infrequent sessions create soreness and fatigue that bleeds into games. Small, frequent exposures maintain neuromuscular qualities without the cost. We train enough to maintain and express, not enough to interfere.

Stack Stress, Do Not Scatter It

The other half of the in season model is stress consolidation. Every day gets classified: are we stressing the system or recovering it? High days stack high intensity work together. Low days are truly low. What we eliminate is the gray zone, those moderate everything days that accumulate fatigue without driving adaptation.

A colleague of mine once said that medium only works in clothing sizes. He was right. A day that is ‘kind of hard‘ and ‘kind of long‘ does not make anyone better. It just makes them tired. Force every session into high intent or genuine recovery, and the week starts to make sense.

This requires alignment with the coaching staff on practice design, because practice is the primary controllable environment. If the plan calls for a low day and practice runs two hours of live scrimmaging, the system breaks. That is why the communication layer matters as much as the training layer.

Clearance Does Not Equal Readiness

One principle I hold as non negotiable: medical clearance is not the same as performance readiness. Medical manages tissue health. Performance builds capacity. Basketball applies demand. An athlete can be cleared and still not ready to handle game demands.

This is where the professional boundary between medical and performance becomes critical. Performance is adjacent to medical. We support, we collaborate, we align around athlete care. But clinical decision making, medical status, and treatment belong to the medical staff. Full stop.

There is a temptation in high performance environments to help everywhere. You see a gap, you fill it. But an eagerness to help can slowly erode professional swim lanes, especially near scope of practice lines. I have learned that sometimes the most respectful thing you can do is stay in your lane and let the expert in the next lane do their job.

Respect can look like restraint.

The System Is Also the People

The training framework is only half the system. The other half is the department itself: who owns what, who decides what, and how information moves between specialized roles.

As a performance department grows, you add capacity. A sport scientist, a dietitian, an assistant coach, an analyst. Each one makes the department better. But each one also creates a new question: who owns the decision when domains overlap? If nobody answers that question explicitly, the answer becomes whoever acts first. That is not delegation. That is ambiguity wearing a nicer name.

I use a simple framework for role clarity. Every task gets five questions: who is Responsible for executing it, who is Accountable for the outcome, who Supports the work, who needs to be Consulted before a decision, and who needs to be Informed after. It takes ten minutes to fill out and saves months of friction. The point is not bureaucracy. The point is that assumptions are where departments break down.

Delegation Versus Displacement

This is the distinction I think about most as a director. Delegation is when a specialized staff member owns execution with clear visibility back to the larger system. Displacement is when a specialized lane starts making directional decisions without a loop back to the person expected to integrate the whole.

They look similar from the outside. Both involve trusting good people to do good work. The difference is information flow. In delegation, the director stays connected to decisions that affect the broader performance model. In displacement, the director finds out after the fact and has to reverse engineer what happened and why.

Neither is about competence. I have worked with outstanding practitioners on both sides of this line. It is about structure. If you do not build the communication loops explicitly, you will get displacement by default, because talented people will fill every vacuum you leave.

The fix is not micromanagement. It is clarity. Be explicit about which decisions roll up and which ones stay in the lane. Then trust people inside the structure you built.

Simplify Until the Coach Gets It

All of this complexity has to collapse into something a head coach can use in thirty seconds. My communication standard is simple: here is the status, here is the recommendation, here is why. One answer, not multiple opinions.

We do not need more data. We need clearer answers. A report that requires an explanation has failed. Daily readiness, practice load, weekly trends, all of it should be immediately readable by someone who does not live in the data. Color codes, clear status categories, one final recommendation per athlete.

This is also where trust gets built. Trust is earned through predictability, not personality.

When the coaching staff gets the same clear format every day, with recommendations that hold up, they stop questioning and start following. That is when the system actually works.

Development Across Six Months

Most people treat a professional basketball season as a survival exercise. Keep everyone healthy, get to October, do not break anything. Survival is the floor, not the ceiling.

Athletes can still develop in season if your system is built for it. Not every quality, not every week, but the right quality at the right time. A player who only maintains for six months is not the same player in October. She is a slightly worse version, held together by caution. The teams that win late are the ones whose athletes are still improving in small, specific ways when it matters most.

Microdosing, stress consolidation, and the daily decision model are how you do this. Small exposures, clearly classified days, and a readiness system that tells you when to push and when to pull back. It is precision work inside a chaotic environment. That is the job.

What I Would Tell a Younger Director

Define your North Star before you build anything. Stop trying to control the season, you will not. Build the training system that bends, build the department structure that clarifies, communicate in a way that a busy coach can actually use, trust the athlete report as much as the data, and remember that keeping players healthy and developing for six straight months is one of the hardest things in this profession.

And define who owns what before you need to. The conversation about governance is always easier before the friction than after it.

This is the first entry in my Director's Notebook, a series on the decisions behind the programs. Not the methods. The calls. I will keep writing them as long as they are useful.

If this resonated, I keep a small library of free tools for coaches: checklists, frameworks, and calculators from twenty years in the profession.

Take what is useful.