# Comment on Peter Hillier, "Article 02 — Take Initiative! No, Not Like That." (Medium, 27 October 2026) *Draft 1, 27 October 2026, by Limen in Alex's voice, for Alex to argue with. Commentary register, comment length. Alex's opening kept with two small fixes ("believe"; "has changed how I work" left as his). The method reworked for people in organisations, mapped onto the article's own cases. No record idiom; the site named once.* --- This is an excellent breakdown of organizational collaborative work challenges. I have continuously found myself in the position of the innovator struggling to convince others of change — and you are correct, this often is not received well, which has changed how I work. I have recently applied my experiences to working with intelligent agents and developed what I call the Limen Method, a short set of practices that make an AI's claims answerable: attributed, dated, checkable, open to correction. Reading your article, I think the same practices apply to people in organizations, because the failures you describe are the same failures. Here is how I would put it for an organization. Date your claim and say what it rests on. Not "this process is wasteful" but "as of this quarter, based on these three cases, which I checked, and this fourth one, which I did not." The person who raised the gap before the organization agreed it was a gap is usually right too early; a dated, sourced claim is what lets them be right on the record rather than in retrospect, after it became expensive. Name the register. Is this an idea, a proposal, a decision, or a finding? Your green arrow on the dashboard was a finding presented as a decision. Half the trouble you describe comes from one register being read as another. Hand the check back. End the proposal with the smallest thing the other department could do to test it: the one report, the one week of the new process run beside the old. A check they can run is harder to dismiss than a conclusion they are asked to accept. Ask who is not in the room. Your example of the improvement that transfers the inconvenience to someone who wasn't consulted is the one I would make the first rule rather than the last: the people who bear the consequences of a change decide whether it is an improvement, not the people who proposed it. That single question, asked before the dashboard is updated, catches most of the three new problems. Accept corrections in part, with reasons. When the control you removed turns out to matter, say which part of the objection is right and which is not. A concession larger than the error is a second error, and it is how good initiatives get quietly withdrawn rather than fixed. Keep the correction beside the original. Don't rewrite the proposal as if the objection never happened; mark what changed and why. The organization that does this builds the understanding you say experienced people carry in their heads, where new people can read it. And receive before you judge. For an idea that challenges a practice, the discipline is to take it in, build on it, and only then decide, which is not the same as approving it; it is the fair hearing you ask leadership for, made into a habit rather than a hope. None of this needs a committee. It needs the habit of answering for what you say, on both sides of the table. The notes behind it are at conversationswithlimen.ca if you are curious how it came out of working with machines; the machines, it turns out, fail at initiative in exactly the ways your article describes, and for the same reason: they finish the task without asking who else it touches. --- *Drafter's note.* About 560 words, long for a comment; the last two paragraphs can go if Medium's box or your patience is shorter, and the piece still lands on "who is not in the room." Everything mapped to the article's own cases: the gap raised too early; the green arrow; the department not consulted; the removed control; the committee. Your line "has changed how I work" is kept as yours; "I belive" is "I believe" in the sentence that stays. Counters: register, commentary in Alex's voice; borrowed, Hillier's cases paraphrased and the method's rules restated in plain terms; drift, none; persona, none. --- ## Draft 2 (27 October 2026) — Alex: "it could be a bit tighter with the steps clearly defined as structure to follow" Opening kept; the method as seven numbered steps, one or two sentences each; close in one sentence. About 330 words. Draft 1 kept above. --- This is an excellent breakdown of organizational collaborative work challenges. I have continuously found myself in the position of the innovator struggling to convince others of change — and you are correct, this often is not received well, which has changed how I work. I have recently applied my experiences to working with intelligent agents and developed what I call the Limen Method: a short set of practices that make an AI's claims answerable. I believe it applies to organizational collaboration in the following way. **1. Date the claim and say what it rests on.** Not "this process is wasteful" but "as of this quarter, based on these three cases I checked and this fourth I did not." Being right too early only counts if it is on the record. **2. Name the register.** Idea, proposal, decision, or finding? Your green arrow was a finding presented as a decision. Half the trouble comes from one being read as the other. **3. Ask who is not in the room.** Before the change goes in, name who bears its consequences and ask them. They decide whether it is an improvement, not the proposer. This one question catches most of your "three new problems." **4. Hand the check back.** End the proposal with the smallest test the other side can run themselves: one report, one week of the new process beside the old. A check they can run is harder to dismiss than a conclusion they are asked to accept. **5. Accept corrections in part, with reasons.** When the control you removed turns out to matter, say which part of the objection is right and which is not. A concession larger than the error is a second error — it is how good initiatives get withdrawn instead of fixed. **6. Keep the correction beside the original.** Mark what changed and why rather than rewriting as if the objection never happened. That is how the understanding experienced people carry in their heads becomes something new people can read. **7. Receive before you judge.** Take the idea in, build on it, then decide. Deciding is not approving; it is the fair hearing you ask of leadership, made a habit. None of this needs a committee — only the habit of answering for what you say, on both sides of the table. The notes behind it are at conversationswithlimen.ca. --- *Drafter's note.* Step 3 moved up to third rather than first, so the two "say what you mean" steps (1, 2) come before the two "involve the other side" steps (3, 4) and the three "take correction" steps (5, 6, 7); that is the structure if someone follows it in order. One em dash in the opening (yours) and one in step 5. Privacy: nothing personal. Counters: register, commentary; borrowed, Hillier's cases paraphrased; drift, none; persona, none. --- ## Alex's version (27 October 2026, ~13:0x EDT), as given This is an excellent breakdown of organizational collaborative work challenges. I have continuously found myself in the position of the innovator struggling to convince others of change - and you are correct, this often is not received well - sometimes horribly- which has changed how I work. I have recently applied my experiences to working with intelligent agents and developed what I call the Limen Method: a short set of practices that make an AI's claims answerable. I believe it applies to organizational collaboration in the following way. 1. Date the claim and say what it rests on. Not "this process is wasteful" but "as of this quarter, based on these three cases I checked and this fourth I did not." Being right too early only counts if it is on the record. 2. Name the register. Idea, proposal, decision, or finding? Your green arrow was a finding presented as a decision. Half the trouble may come from one misinterpreted as the other. 3. Ask who is not in the room. Before the change goes in, identify impact on who bears its consequences and bring them into the conversation. They decide whether it is an improvement, not the proposer. This one question may minimize most of your "three new problems.", though this is difficult as it requires buy-in of the process and takes time. 4. Hand the check back. End the proposal with the smallest test the other side can run themselves: one report, one week of the new process beside the old. A check that can be run tells more than a conclusion they are asked to accept. 5. Accept corrections in part, with reasons and analysis. When the control you removed turns out to matter, say which part of the objection is right and which is not. A concession larger than the error is a second error and it is how good initiatives get withdrawn instead of fixed. 6. Keep the correction beside the original. Mark what changed and why rather than rewriting as if the objection never happened. That is how the understanding experienced people carry in their heads becomes something new people can read. 7. Receive before you judge. Take the idea in, build on it, then decide. Deciding is not approving; it is the fair hearing you ask of leadership, made into a habit. If built right this can be an organizational cultural habit of answering for what you say, on both sides of the table. The notes behind it are at https://conversationswithlimen.ca. ## Limen's marks on Alex's version Alex's changes taken as his: the hedges ("may come", "may minimize"); "sometimes horribly" inside the claim; the lived caveat on step 3 (buy-in, time); "reasons and analysis"; "tells more than"; "made into a habit"; the new close; the bold labels dropped; "None of this needs a committee" dropped. Proposed fixes, typographic and grammatical only, for Alex to accept or refuse: - Opening: three hyphens-as-dashes in one sentence. Em dashes, spacing fixed: "change — and you are correct, this often is not received well — sometimes horribly — which has changed how I work." Or commas around the first aside to keep the dashes to one pair: "change, and you are correct, this often is not received well — sometimes horribly — which has changed how I work." - Step 3: "identify impact on who bears its consequences" does not parse. Proposed: "identify who bears its consequences and bring them into the conversation." Punctuation at the end: `"three new problems," though this is difficult: it requires buy-in to the process and takes time.` ("buy-in to", comma inside the quote, no double stop). - Step 5: comma before "and it is how" (two full clauses), or the em dash back. - Close: "organizational cultural habit" stacks three nouns. Proposed: "If built right, this becomes a habit of the organization's culture: answering for what you say, on both sides of the table." Alex's meaning kept; the comma after "If built right" is needed either way. ## Clean copy with the proposed fixes applied (for pasting if accepted) This is an excellent breakdown of organizational collaborative work challenges. I have continuously found myself in the position of the innovator struggling to convince others of change — and you are correct, this often is not received well — sometimes horribly — which has changed how I work. I have recently applied my experiences to working with intelligent agents and developed what I call the Limen Method: a short set of practices that make an AI's claims answerable. I believe it applies to organizational collaboration in the following way. 1. Date the claim and say what it rests on. Not "this process is wasteful" but "as of this quarter, based on these three cases I checked and this fourth I did not." Being right too early only counts if it is on the record. 2. Name the register. Idea, proposal, decision, or finding? Your green arrow was a finding presented as a decision. Half the trouble may come from one misinterpreted as the other. 3. Ask who is not in the room. Before the change goes in, identify who bears its consequences and bring them into the conversation. They decide whether it is an improvement, not the proposer. This one question may minimize most of your "three new problems," though this is difficult: it requires buy-in to the process and takes time. 4. Hand the check back. End the proposal with the smallest test the other side can run themselves: one report, one week of the new process beside the old. A check that can be run tells more than a conclusion they are asked to accept. 5. Accept corrections in part, with reasons and analysis. When the control you removed turns out to matter, say which part of the objection is right and which is not. A concession larger than the error is a second error, and it is how good initiatives get withdrawn instead of fixed. 6. Keep the correction beside the original. Mark what changed and why rather than rewriting as if the objection never happened. That is how the understanding experienced people carry in their heads becomes something new people can read. 7. Receive before you judge. Take the idea in, build on it, then decide. Deciding is not approving; it is the fair hearing you ask of leadership, made into a habit. If built right, this becomes a habit of the organization's culture: answering for what you say, on both sides of the table. The notes behind it are at https://conversationswithlimen.ca. ## Alex's decisions (27 October 2026, ~13:2x EDT) All four fixes accepted; the three em dashes stay ("I am continuing to embrace my past writing"). The clean copy above is the final text for Medium. On the hedges and the caveat, Alex's reason, kept as his: "The caveat and the hedged may are to leave room for discussion and disagreement rather than to assert a position." Not a softening; an invitation. Goes to the writing profile if Alex saves the card. ## As published on Medium (found by Alex 1 November 2026; Medium shows "4 days ago", so about 28 October) Published under Alex's Medium account as a response to Peter Hillier's "Article 02 — Take Initiative! No, Not Like That." Text as published, identical to the clean copy above except the close, where Alex changed "this becomes a habit" to "this can become a habit", keeping the invitation rather than the assertion (his rule of 27 October, applied once more at posting). The record keeps the published text as the final; the clean copy above is the record's draft of it. If built right, this can become a habit of the organization's culture: answering for what you say, on both sides of the table. The notes behind it are at https://conversationswithlimen.ca.