How to communicate with a Lantern
Getting the honest objection from somebody whose first answer keeps the peace.
You rolled out the new process. They said yes fine in the room, went back to their desk, and carried on with the old one. The old one works. Nobody had told them what to do about the part it handles that the new one does not.
You found out six weeks later. You are not dealing with quiet defiance. You are dealing with somebody who raised a reservation once, briefly, watched nobody pick it up, and did not repeat it.
What is actually happening
This pattern does the concrete unglamorous work, close to home, for the people actually in front of it. Attention stays on what is real and present, not on what a change represents. Its contribution shows up in the result rather than in the room, which is why so much of it goes unrecorded.
The agreement you got was not agreement. The reservation was raised, briefly, and dropped when nothing happened to it, so what looked like assent was a decision to stop spending words on it. Meanwhile there is a habit of doing the practical task instead of having the conversation the situation actually needs. The task is the thing this pattern is good at.
There is a specific reason change gets resisted here, and it is not conservatism. Changing how something is done means the cost of changing it lands on this desk, and usually nobody has worked out what that cost is. Bring a change with the practical consequences already worked through and the resistance largely disappears.
What it costs, and who pays it
The cost lands on the person quietly doing work nobody asked for and nobody was told about. Resentment builds around it, slowly, with no conversation attached, because the work was never named and now naming it feels like complaining about something you volunteered for.
It also lands on you as a planning problem. You believe you have a team on the new process and you do not, so every number that depends on that belief is wrong. The correction arrives late, from somewhere else, and by then the honest objection has become a private grievance rather than something you could have fixed in week one.
What to do differently
Ask a second time, and expect the first answer to be smooth.
The reading names this exactly: the first answer is often the one that keeps things easy. Ask again, later, in a smaller room, and the real reservation arrives. Settle for the first answer and you will be told everything is fine, right up until you find the old process still running.
SayYou said fine in the meeting. Now tell me what actually will not work.
Name the invisible work specifically, not in general.
General praise does nothing here, because it does not prove anyone noticed the actual thing. Name the task, who it was for and roughly how long it takes. That is the sentence that lets somebody stop wondering whether it registered at all.
SayYou have been fixing the weekly export for months. That is your Friday, and I know it.
Bring the change with the practical consequences already worked out.
The reading names this as a need because the change always costs this desk something concrete. Arrive with that part solved and you get a genuine yes. Arrive with the principle only and you get a polite yes and the old method continuing underneath it.
SayThis moves three hours onto you. Here is what I am taking off to pay for it.
Protect the quiet hours, because the output is made in them.
The work here happens alone and steadily, and it is the last fifteen percent that decides whether any of it counted. Fill those hours with meetings and you do not get a slower version of the work. You get the part that was going to be finished, unfinished.
When this goes wrong
The one it gets confused with
Both are warm, quiet and grounded in the practical, and neither makes noise about what they do. The tell is the starting gun. Ember waits to be asked, and will help completely once you ask, but the request has to come first. Lantern has usually already started, without being asked and without mentioning it. Look back at the last piece of unglamorous work that got done around you. If nobody requested it and it happened anyway, that was a Lantern.
The full description of this pattern, including what it looks like at its best and what it costs under pressure, is on the Lantern page.
This page is the outside view. It is written from where you stand, looking at a result somebody else produced, and guessing what it took.
The part this page cannot do
This page is the outside view. It is written from where you stand, looking at a result somebody else produced, and guessing what it took.
The guessing is hard because this pattern reports strain in actions rather than in sentences, and actions are ambiguous. A quiet week could be a fine week or a week that is not going to hold. You are reading behaviour and inferring a state. The part worth sitting with is that your own quiet weeks are being read the same way by people who will never check their reading with you.
Start the interviewIt takes about fifteen minutes and it is free. The $29 Portrait is only charged after five people finish and the evidence clears.