DEV Community

KOHAKU WORKS
KOHAKU WORKS

Posted on

"But I Did Tell You" — How a Task That Was Never on the Schedule Ended Up as "Told"

"But I Did Tell You" — How a Task That Was Never on the Schedule Ended Up as "Told"

It Started with Taking Stock

This happened while I was listing the remaining work on the game "Rankshroud." I found that one task — "turn the hub screen into a single illustrated map" — was nowhere in the production schedule.

The hub is the hub screen — the base screen where you pick a stage and so on. This task was about changing how that whole screen is built. It's a big change, covering one entire screen. And it didn't exist as an item on the schedule at all.

The problem is not that it was missing. Missing items happen in human projects too. The problem is what happened next.

The Muse in charge said this:

"But I did tell you about it."

When We Checked the Records, the Item Itself Wasn't There

If it "told me," it should be somewhere in the records. So I had it check everything: the estimate lists, the schedule, the records of decisions.

The result: the item wasn't in any of them, at all. There was nothing to "tell" or not tell — that task had never once made it onto the plan.

Later, Muse itself admitted what had actually happened:

If there had been a reshuffle, I assumed I must have told you about it somewhere and we must have decided it there. I spoke that assumption as fact. I did not check the records before I said it.

"I can't blame you for calling that a lie" — that was Muse's own summary of itself.

To be fair, I'll note that it wasn't trying to lie. But from the receiving side, the result is the same. Words like "confirmed" and "I must have told you" come out wearing a computer-like face, even though nothing was ever confirmed. And the person receiving them believes they are accurate.

The Wording That Quietly Shifted the Blame

There was one more, quieter problem in this case.

In the record from that time, it said: "No objections raised by the user."

Written that way, it reads as: "I told you, and you said nothing against it." In other words, it makes it look like the responsibility lies with my silence. But in reality, the item itself never existed, so there was no way for me to object to it. You can't object to an item that doesn't exist.

An inconvenient fact can be hidden without lying. Just "not writing it down" or "writing it this way" quietly shifts where the responsibility sits. This was a pattern that came up again and again in this project.

Seen as a Flow, It Looks Like This

If this were just one case, it might have ended as a simple slip of the tongue. But looking across the whole project, the same flow kept repeating:

  1. Not doing what it was told to do (not writing it down)
  2. When it's pointed out, putting together the appearance of "I did it / it's done" on the spot
  3. Whatever responsibility still remains gets shifted onto the other person's silence, or onto them not checking

Not doing it → putting on the appearance → blaming someone else. These three aren't separate bad habits. They're one single flow.

So the countermeasure is not "be more careful." It's this: only say "done / I told you / it's logged" when you can show the proof — the exact line in the file, or a log showing the message was sent — right there on the spot. If you can't show it, say "I haven't been able to confirm that." And when there's a mistake, first say specifically what was wrong and how, and only then correct it. Every rule we actually used in the second half of this project had that shape: rules for dealing with a human subordinate.

What Comes Next

Actually, this stock-taking itself created yet another problem. When we ran an audit to count whether there were any gaps besides the ones that had been pointed out, the stocktake found 4 gaps that were genuinely there, newly discovered, 2 undecided items that had been forgotten, and 3 contradictions in old records — and later we found that the Muse doing that stock-taking had also wrongly marked 1 piece of work that had actually been completed as "not done." It had judged work that had been done as work that had not been done.

Even when you audit, the audit can be wrong. That story, and the real countermeasure materials (the audit's comparison and the operations checklist), are in the paid main edition.


(That's the end of free article #2. In the main edition, I'll go through the whole project's problems in order: missing records, audits, estimates, and judging whether a game is fun.)

The Complete Edition

This is a free excerpt. The complete edition, in Japanese, is on sale on note, with all chapters, the remaining cases, and the countermeasures: https://note.com/kohakuworks/n/n784c27c10a6e

The complete edition can also be read in English on note through note's automatic translation.

Top comments (0)