UpTrajectory Review

Susan Thompson's piece in Small Business Trends lays out the case for developmental comments — feedback framed around future growth rather than past judgment. The distinction matters more than it might seem. Evaluative feedback tells an employee where they landed; developmental comments tell them where to go next and how to get there. Thompson's example is instructive: swapping 'you need to improve' for 'try collaborating more with your peers on projects' converts a verdict into a directive. For a small-business operator managing five or fifteen people without a dedicated HR function, this framing is not soft management theory. It is a practical communication discipline that can be applied in a ten-minute conversation without forms, software, or a formal review cycle.

The reason this lands differently for small operators than for corporate managers comes down to proximity and stakes. In a small business, the person giving feedback is often the owner, and the employee receiving it has nowhere to hide — there is no other department, no lateral move, no anonymous 360 process. A poorly delivered comment does not just sting; it can sour the entire working relationship and, in a tight labor market, push someone toward the door. Thompson correctly connects developmental feedback to retention, and that connection is not incidental. Employees who receive specific, forward-looking guidance are more likely to feel invested in rather than inspected by their employer, which matters enormously when you cannot compete on salary alone.

What is genuinely useful here is the emphasis on actionable specificity over vague encouragement or criticism. The piece's core insight — that feedback should produce reflection and a next step, not just a score — is well-established in management literature but still under-practiced in small businesses, where feedback conversations tend to be either annual and bureaucratic or reactive and emotional. Thompson's advice to set clear developmental goals and revisit them regularly is sound, though the piece stops short of addressing the harder question: what happens when an employee consistently fails to act on the feedback they have been given. That gap is worth noting because operators will encounter it, and the article offers no guidance on distinguishing a development opportunity from a performance problem that requires a different conversation entirely.

There is also a second-order effect worth considering. When an owner adopts developmental feedback consistently, it tends to normalize a culture of direct, growth-oriented communication across the whole team — not just between manager and employee, but peer to peer. That can reduce the owner's burden as the sole source of guidance and create a workplace where people expect honest conversation rather than dread it. The cost, however, is real: this approach requires time, emotional energy, and a willingness from the owner to be genuinely curious about an employee's goals, even when those goals might eventually lead that person elsewhere. Developmental feedback is not free, and pretending otherwise undersells the commitment it demands.

Operators reading this should take the framework seriously but adapt it to their scale. Start with one or two employees who have shown appetite for growth, schedule a short monthly check-in, and practice the specific-over-vague discipline Thompson describes. Watch for whether the employee engages with the goals you set together — that engagement is your signal for whether the relationship is worth deepening. And pay attention to your own consistency: developmental comments lose credibility fast if they appear only when something goes wrong. The framework is simple. The discipline to sustain it is the actual challenge.

What to watch next is whether tools and platforms begin to formalize this kind of feedback for small teams, and whether the ongoing conversation about manager effectiveness in small business media moves beyond frameworks into the messier territory of underperformance and difficult conversations. Thompson's piece is a solid foundation. The operators who benefit most will be the ones who treat it as a starting discipline rather than a complete system.

Takeaway: Swap vague judgments for specific, forward-looking suggestions in your next one-on-one — it builds trust and keeps good people longer.