Draft
Why texting rules never fix the group text
You can post all the texting rules you want. Here is why every one of them dies in two weeks, and what the crew thread actually needs instead.
You have tried the rules. Most owners have. At some point the crew thread got loud enough that you posted a message like: from now on, job talk only, no memes, no lunch runs, and everybody thumbs-up so I know you saw it. You meant it. For about a week it even held. Then a guy sent a funny photo, somebody answered with a coffee order, and by the end of the second week the thread looked exactly like it did before you posted the rule.
That is not your crew ignoring you. It is the tool doing what it was built to do. A group text is one open room where everyone talks at once. You can ask people to behave inside that room, but you cannot ask the room to become something it is not. The rules keep dying because there is nothing in a text thread for a rule to hang on. This is the same wall the crew thread hits on any small company, and no policy you post moves it.
The rules owners actually try
Run a small shop long enough and you cycle through the same short list of fixes. Each one is a reasonable idea. Each one dies the same way.
Job talk only. The most common rule, and the first to fall. The problem is that the crew is not wrong to send the other stuff. They are together all day, the thread is where they are, and a coffee run genuinely needs a reply. You are asking one channel to be both the break room and the work order, then blaming people for using it as a break room.
Everybody thumbs-up to confirm. This one dies quietly. The first week you get five reactions on every message. By week two you get three, because two guys were driving. By week three the ones who forgot are the ones who most needed to see it, and you still cannot tell the difference between a man who read it and a man who tapped a reaction without reading. A thumbs-up is not proof anyone acted, which is the whole fight behind “I never got the message”.
No memes, keep it clean. Fine until the day the job is going well and someone is in a good mood. You are now the person who polices jokes, which costs you more goodwill than the memes ever cost you time.
Start a new thread for each job. The right instinct, the wrong tool. Now you have six threads, nobody remembers which one the Hendricks job lives in, half the crew is not in the newest one, and the address you posted is in a thread three guys muted last month. You did not fix the mess. You made six of them.
The ten-rule policy that lasted a week
The version that gets passed around the trade forums goes like this. An owner finally snaps after a missed change order and writes out a real policy: ten numbered rules. Job traffic only. Confirm every dispatch with a thumbs-up. Addresses go in by 6 pm the night before. Photos get a caption saying which job. No personal talk before 5 pm. And on down the list. He posts it to the thread, pins it, reads it out at the Monday huddle.
By Friday of that same week it was dead. Not because the crew rebelled. Because rule four, caption every photo with the job, asks a man on a roof with gloves on to type a sentence before he can send a picture, and he is not going to, so he just stops sending the photo. Rule two, thumbs-up every dispatch, turned the thread into a wall of reactions nobody could scroll past to find the actual message. Every rule added friction to a tool that only survives because it has none. The policy did not fail from weak enforcement. It failed because it was ten manual patches over four missing parts, and a person cannot hold four missing parts in his head while running a crew.
What the rules were reaching for
Look at that list again and a pattern shows up. Every rule an owner writes is trying to bolt one of three things onto a channel that was never built to hold it.
A place per job. Job talk only, caption the photo, start a new thread: all of these are you trying to sort one stream into jobs by hand. You are doing the filing that the tool should do. The thread has no concept of a job, so you become the concept.
A status per task. Thumbs-up to confirm, reply when it is done, tell me if you are stuck: these are you trying to invent states on messages that have none. A text says “capped it” and a text says “on my way” in exactly the same flat voice. You cannot see at a glance what is open, what is done, and what is waiting, so you ask, and asking is the thing you were trying to stop.
A name on done. Who locked up, who signed off, who actually looked at the finished work: the rules that ask people to speak up are reaching for accountability the thread cannot record. When done has no name attached, you find out who owned it only after the callback, which is far too late to matter.
Those three things, a place, a status, a name, are not habits your crew is failing to build. They are parts your tool does not have. You have been trying to write a policy that supplies missing parts, and no policy can do that.
The fix is structure, not discipline
Here is the turn. You do not have a discipline problem. Your crew is not lazy and you are not soft for failing to enforce ten rules. You have a tool problem, and the answer is not a better rule. It is a channel that already has the parts the rules kept reaching for.
Give each job its own thread, and job-talk-only stops being a rule because the job already has its own place. Let a task carry a state that someone marks and someone else checks, and thumbs-up stops being theater because done is a real status with a name on it. Let a photo land on the task it proves, and caption-every-photo stops mattering because the picture is already filed. When the structure holds the job for you, most of your rules disappear, because the thing they were fighting to prevent can no longer happen. Getting tomorrow’s plan to the crew stops being ten texts and a confirmation policy, and becomes one post per job that stays put.
That is the whole idea behind Crewmigo. It is the group text your crew already knows how to use, except each job has its own thread that remembers, the work carries photo proof when the job calls for it, and done is a status someone marks, someone approves, and someone signs off. We are new, so put one job on it and watch. You will notice you stopped writing rules, because there was nothing left to police.
Crewmigo runs every job in a thread your crew already knows how to use, with the photo that proves it and a sign-off that closes it. One plan, one price a head. Subs ride free.
Start a job