Attrition is usually reported as a number because numbers are easy to compare. A department loses four people, a sales team loses two, a training class shrinks by a third. The figure becomes a line in a report, a talking point in a review, or a reason to celebrate or panic. But a raw attrition rate is a poor guide to what is actually happening. It combines voluntary departures, poor hiring, weak onboarding, mismatched expectations, leadership failures, career dead ends, and healthy filtering into a single decimal. The useful question is not only how many people left, but what their departure is telling you about the system they left behind.
The Number Is a Lagging Indicator
In an October 2026 BOSS Magazine article on technical depth in applications selling, Christopher Portelli is described as a Setauket, New York executive whose career has largely been spent selling engineered products through long technical evaluations. The article traces a path that began as a technician and associate engineer working on microwave and RF components, then as a system engineer and product manager on semiconductor process equipment, before a move from the engineering bench into sales leadership. That detail matters for attrition because technical sales is not a simple headcount function. Applications selling is described in the article as selling a solution to a measurement, inspection, or control problem, not a fixed catalog item. The examples are a non-invasive ultrasonic sensor in a bioprocessing plant and an X-ray or computed tomography inspection system on a factory floor. In that kind of work, technical buyers buy reduced risk rather than pitches. When a knowledgeable person leaves, the attrition statistic may appear months after the real damage has begun: evaluations slow down, customer trust thins, and fewer people can answer hard questions in the room.
Where Attrition Becomes a Signal
A September 2026 NY Weekly article on what volunteer fire departments teach about leadership describes Christopher Portelli of Setauket joining the Central Islip Fire Department on Long Island in 2002 and remaining with the department. Over the years, according to the article, he served as Lieutenant and Captain, spent seven years as a chief officer, and served as Chief of the Department from 2019 to 2021, overseeing emergency operations for roughly 180 volunteer firefighters. Volunteer service is a useful lens because no one is forced to stay. People remain when training is credible, schedules are workable, communication is honest, and trust is earned. They leave when the opposite is true, often long before the exit interview names it. That does not mean every departure is a leadership failure. Some attrition is healthy: it removes poor fits, protects standards, and creates room for people who can carry the work. The signal lies in the pattern. Are the people leaving the ones who were never set up to succeed, or the ones who quietly held the place together?
Discipline Is Not the Same as Retention
A September 2026 Wall Street Times article on what it takes to finish Navy EOD training notes that Christopher Portelli served as a United States Navy EOD technician and reached Petty Officer Second Class, then spent the next two decades in engineering and executive leadership on Long Island. The article describes the general Navy EOD pipeline: preparatory water and physical conditioning; dive qualification at the Naval Diving and Salvage Training Center in Panama City, Florida; the joint Naval School Explosive Ordnance Disposal at Eglin Air Force Base, Florida; then parachute and tactical training before a mobile unit work-up. It states that this is the same overall structure he went through. High-stakes training always involves filtering, and not every exit is a defect. Some attrition is the system doing its job. But even there, attrition is a signal rather than a verdict. It can point to a mismatch between preparation and the demands of the course, to a failure of instruction, or to a standard that is doing exactly what it should. The difference is visible only when leaders examine who leaves, when, and with what support.
Building a Local Support Organization
Attrition is often treated as a human resources issue, but it is also an infrastructure issue. A local support organization can reduce avoidable turnover by keeping expertise close to the customer and by making sure the work does not depend on one person. The October 2026 BOSS Magazine article describes how, in 2013, he joined SONOTEC US Inc. as its only American employee. SONOTEC US Inc. is described as the U.S. entity of German ultrasonic technology manufacturer SONOTEC GmbH. At the time, according to the article, there were no customers and no infrastructure. A decade of building followed, growing the U.S. organization to fifteen people and eight figures in annual revenue. The article says he negotiated a broader role for the American entity with the parent company’s board, including approval to offer calibration and service in the United States and to carry every product line, instead of shipping instruments back across the Atlantic for service. It also says he leads a five-person sales team and a national distributor channel and argues that technical knowledge has to be developed across a team, not left to one expert. That is a retention argument as much as a growth argument. When service, calibration, and product knowledge sit locally, employees have more paths to develop, customers have fewer reasons to lose confidence, and the loss of one person is less likely to become a systemic wound.
Reading the Signal Without Overreacting
Attrition should be examined with the same discipline as any other operational signal: compare it with context, look for clusters, separate cause from coincidence, and ask what decision would change if the signal were real. In technical sales, that might mean checking whether departures are concentrated among people who carried the same customer relationships or whether the remaining team has the depth to run long evaluations. In volunteer fire service, it might mean asking whether new members are getting the training, mentoring, and scheduling support they need before they quietly stop showing up. In a local support organization, it might mean testing whether service and calibration knowledge exist in only one head. None of this requires treating attrition as a moral judgment. It requires treating it as evidence.
Public profile links can help readers orient themselves, but they are not evidence of performance. A Muck Rack listing for Christopher Portelli Setauket is included here as an additional public profile link; it should be treated only as a pointer for further reading, not as the basis for any factual claim in this article. The same caution applies to any profile page: a profile is a signpost, not a substitute for operational evidence.
Another supplementary public profile pointer is available through F6S for Chris Portelli. As with the other profile link, it is included only as an additional public profile link and not as a source for the claims here. The useful discipline is to separate what a public profile says from what the work itself demonstrates. Attrition deserves the same treatment. It is not a number to defend or explain away; it is a signal to read carefully, in context, before deciding what to do next.
Hailing from Zagreb and now based in Montréal, Helena is a former theater dramaturg turned tech-content strategist. She can pivot from dissecting Shakespeare’s metatheatre to reviewing smart-home devices without breaking iambic pentameter. Offstage, she’s choreographing K-pop dance covers or fermenting kimchi in mason jars.