Content Pillars
Category: strategy Sources: Thought Leadership skill session (2026-07-30) Confidence: high Last Updated: 2026-07-30
Four pillars, built through the Thought Leadership skill. Each one is a complete teachable unit: a real story, a quotable point, a named framework and one concrete action. Read through the one-word lens set in Positioning — Problem: Exposed, Solution: Covered.
1. How the System Actually Works
Problem it solves: Believing the test house will catch your mistakes for you, when the responsibility for submitting the right thing has never once been theirs.
Story: A brand's first range went through us with a lot of eyes on it and a lot of pressure to get it right. Everything passed testing and it was sitting with the certification team, the final stage. Then the "final" garments started arriving so we could check them against the technical files, and they weren't what had been tested. A jacket had gone from three-layer to two-layer construction, silently making the abrasion result that had passed redundant. Trousers had stretch panels added into a construction that had never been tested at all, only the previous outer shell had. Everything had to go back through testing. It happened again, and again, three more rounds of "final" samples that weren't final, dragging the whole thing out for months, with a testing bill that kept climbing every time.
Point: A test house tests exactly what you send it. Nobody there is checking your thinking, only your sample, whether it was the right thing to send is entirely on you, and you don't find out until the money and the time are already gone.
Framework: Signature Frameworks — "Your Technical File Is a Passport"
Action: Pull up one live product's technical file and test reports right now. Could you actually match every material listed to what's really in the product? If something's about to go through testing or certification, do this before you submit, not after.
2. Avoidable Mistakes
Problem it solves: Treating a passed test as a permanent status instead of a snapshot of one exact construction, so changes made afterwards quietly invalidate results nobody rechecks.
Story: A brand's first range went through us with a lot of eyes on it and a lot of pressure to get it right. Everything passed testing and it was sitting with the certification team, the final stage. Then the "final" garments started arriving so we could check them against the technical files, and they weren't what had been tested. A jacket had gone from three-layer to two-layer construction, silently making the abrasion result that had passed redundant. Trousers had stretch panels added into a construction that had never been tested at all, only the previous outer shell had. Everything had to go back through testing. It happened again, and again, three more rounds of "final" samples that weren't final, dragging the whole thing out for months, with a testing bill that kept climbing every time.
Point: The most expensive test is the one you didn't need to run. Almost every avoidable mistake in this industry happens before testing even starts.
Framework: Signature Frameworks — "Testing Is a Snapshot, Not a Status"
Action: The next time a "final" sample comes back for anything currently mid-route, physically compare it against the last tested sample, layer by layer, material by material, before anyone calls it final. If anything changed, the test is void until it's redone, no matter how small the change looks.
3. From Live to Covered
Problem it solves: Assuming a range that's already on the market must be compliant, when no one has actually gone back through it product by product to check.
Story: A pattern that shows up more often than it should: a range that had been selling for years on the strength of the factory's word alone, no real certification and no due diligence behind any of it. If one customer had an accident, there would have been no legal ground to stand on. Hiring cycled through one product manager after another, but nothing in the range itself changed, because the missing years of experience were never actually replaced by a new hire. What actually needed to happen, before another product went anywhere near market, was going through everything that already existed and working out what was genuinely a priority.
Point: Being on the shelf isn't the same as being covered. Most ranges stay exactly as messy as launch day until someone actually goes through them.
Framework: Signature Frameworks — "One Cabinet, Every Drawer Labelled"
Action: Pick one product from your live range and try to actually build its drawer right now: every test report, certificate and piece of technical documentation that should exist for it, all in one place. If you can't fill the drawer for a single product, you don't yet know what the rest of the range looks like either.
4. More Hands, Not More Safety
Problem it solves: Believing that adding headcount to a product team closes a technical competence gap, when the specific PPE experience needed was never actually part of the hire.
Story: It's a familiar sight in this industry: fashion designers moving across into PPE brands, and sometimes a brand builds out a whole design team this way, several people deep. None of it moves the needle, because not one of them carries technical knowledge. You can have a full room of experienced designers and still have a range where nobody actually understands what makes a product compliant, because that was never the skill being hired for in the first place.
Point: Hiring more people into your product team doesn't make your products safer. Hiring the person whose experience actually matches the gap does, and that's rarely who's available to hire.
Framework: Signature Frameworks — "The Wrong Toolbox"
Action: List everyone currently on your product team and write next to each name what real PPE testing or certification experience they actually have, not their job title or years in design. If that column comes up empty, the next hire needs to fill it specifically, not just add another name to the list.