Reschema

Transfer a relational structure from another domain.

Your team starts plenty of projects. Finishing them is another story. Everyone looks busy, so the obvious answer is to work harder.

Then you think about a restaurant kitchen. If every order needs the same busy station, starting more orders can add to the pile without getting dinner out any faster. Could the same relationship explain your unfinished projects?

That question is the beginning of Reschema. The borrowed pattern gives you something to investigate: where does work wait, and what is it waiting for? It has not yet given you an answer.

What it is, how it works, and when it helps

A problem can look unfamiliar while having a familiar structure. Reschema means borrowing the relationships from a domain you understand, then checking which of them hold in the new one. A schema is that underlying pattern: what the parts do and how they relate.

In the kitchen comparison, dishes and projects are different things. The potentially useful resemblance is that several pieces of work compete for the same limited capacity. That relationship suggests a question, a prediction, and perhaps a small test.

Use this move when a new subject will not click, a process is stuck, or you need a different way into a problem. It helps most when you know enough about both domains to question the match. If a direct measurement or a known procedure already settles the matter, use it.