An example

Here is what one week in Noemate looks like. He manages an operations team and studies for an Executive MBA at the weekend. This week's class was on organizational behavior. At work, one supervisor keeps missing the handover meeting, the short meeting where one shift passes its work to the next, and each time the manager does the supervisor's part himself. These are his four answers for the week.

His four answers

  1. What happened: I covered the handover again and stayed until 21:00.
  2. What I assumed wrongly: I assumed he did not care.
  3. The lesson: When someone keeps missing a meeting, it is often because something else competes for that time, not because they do not care.
  4. When the lesson is wrong: If he was told clearly that the meeting comes first, and he still misses it.

Then he writes a prediction: "If I move the meeting by 30 minutes, he will come to at least three of the next four." He sets the check date four weeks later.

Four weeks later

  1. What I expected: Three of the next four. (Noemate shows him this. He cannot change it.)
  2. What really happened: He came to two of four. Better, but not three. The real problem was the 17:00 slot. It clashes with the delivery check.

Now he has two notes with dates: what he expected, and what happened. He can see he was partly right, and he knows what to try next. Your first prediction can be smaller, checked in one week.

What he gets from this. The lesson from Friday is still there on Monday: move the meeting, do not blame the person. Four weeks later he knows if he was right. In six months he has a dated example to use when his boss asks what the Executive MBA changed.

This is an illustration, written the way a working student would write it. The people and the events are not real.

Apply for a founding place Next: Try it first