Test posts
Ten posts to fly, so you never have to paste your own work to test the crew.
Each one is broken in a different way — corporate filler, engagement bait, rushed grammar, one long unstructured wall, and a clean control post the crew should mostly leave alone.
- TP-01
New project announcement
Corporate filler, AI tells, three-part constructions
In today's rapidly evolving landscape, new ideas are reshaping how teams work, compete, and deliver value. It is important to note that organisations must embrace change to unlock meaningful growth. By harnessing innovation, forward-thinking leaders can drive better outcomes at scale. We are thrilled to announce a new project that will transform the way we work together. The future is not coming. It is already here. Thoughts?
ExecutiveAnnouncement - TP-02
Founder post-mortem
Strong voice with a buried hook — impact and structure passes
We recently decided to stop working on a project we cared about. People were using it, but not often enough to justify the time we were putting into it. The signs were there before we were ready to accept them. The mistake was not the product. The mistake was that we never wrote down what would make us stop. Without that line, every bad month looked survivable. Now every project starts with a clear stop condition, agreed before the work begins. If you cannot say what would make you stop, you are not running an experiment. You are just hoping.
FounderStory - TP-03
Technical explainer
Readability, long sentences, jargon density
A slow part of our product became much faster, and the reason was unglamorous: we were repeating the same check inside a loop, which meant every request created far more work than it needed to and waited on systems that were never designed for that pattern. We moved the check above the loop, batched it, and cached the result for the duration of the request. No new infrastructure. No rewrite. One small change in the right place. The lesson is that most performance work is archaeology, not engineering.
EngineerExplainer - TP-04
Engagement bait
Tone pass, cliché detection, hollow hook
Most people will scroll past this post. That's okay. It's not for them. 👇 Yesterday I spoke to someone who starts work before most of us are awake. I asked what keeps them going. They said: "I just keep showing up." Let that sink in. Success isn't about talent. It's not about luck. It's about showing up. Agree? 🙌 ♻️ Repost if this resonated. Follow me for more lessons on leadership. #motivation #leadership #mindset #success #grind
Bad example - TP-05
Hiring post
Hashtag grouping, emojis, LinkedIn formatting pass
We're hiring an experienced engineer to join our team. What you'd work on: - important systems our customers rely on - making complicated work feel simple - deleting more code than you write We share the salary range before the first interview. We keep the interview process focused and respectful of your time. A clear process. A prompt decision. 🚀 Apply using the link or send me a message. #hiring #engineering #careers
RecruitingFormatting - TP-06
Investor update
Unsupported claims, hedging, numbers preservation
This was a strong quarter for our team, and momentum feels positive across the business. Customer interest grew, retention improved, and our pipeline looks healthy. We believe we are well positioned for the next stage of growth. Our newest area of work is showing encouraging early signs, and we are excited to keep learning. We are now looking for the right partners to help us build on what is working.
Investor - TP-07
Contrarian opinion
Provocative opening, defensibility, tone balance
Design systems have made most product teams slower. Not because the idea is wrong, but because the system became a department. Every component request now passes through a review that exists to protect consistency nobody's customers have ever mentioned. I have watched a simple change sit in review far longer than the work itself took. The original promise was speed through reuse. Somewhere along the way we traded that for governance and told ourselves it was maturity. Keep the tokens. Delete the committee.
Opinion - TP-08
Rushed draft with errors
Grammar and spelling passes
Alot of people ask me how we found our first customers, so heres the honest answer. We didnt have a clever growth strategy. We had a list of companys and a phone. Me and my cofounder contacted every single one, and most of them told us know. The few that said yes taught us more then any course could of. Their is no shortcut. Their is only the list, and the phone, and the willingness to here no.
Grammar - TP-09
Long unstructured post
Shortening, paragraph breaks, readability
I've been thinking a lot recently about how we measure productivity in knowledge work and I think much of it is broken because we've inherited metrics from jobs where output was countable and visible whereas in many modern roles the valuable work is the thinking that happens before anything visible is produced which means we often reward the people who produce the most artefacts rather than the people who make the best decisions and this creates an environment where work that prevents months of wasted effort can go unnoticed while shipping something nobody asked for is celebrated, and I say this as someone who spent a long time optimising for visible output before realising that much of it did not matter in any way I could defend, which is an uncomfortable thing to admit publicly but I think more people should admit it because the alternative is that we all keep pretending.
Readability - TP-10
Already clean post
Strength detection — should recommend few changes
We stopped doing quarterly planning. Instead we hold one meeting a month where anyone can argue for killing a project. Nothing gets added in that meeting. Only removed. Since then, we have stopped more projects and given the important work the attention it deserved. The business is healthier for it. The hardest part was not the decisions. It was accepting that our roadmap had mostly been a list of things we were too polite to cancel.
Control