A Project Can Show Its Learning Before It Looks Finished

A thought experiment: a student team tests a rough prototype, and it doesn’t work as expected. If they only count the polished final product, that session may look like a failure. But the team may have learned which assumption needs changing—and what to test next.

A small learning record can make that progress visible: write down one assumption, what you tried, what happened, and the next decision. It doesn’t need to become a report; a few lines are enough to help the team carry evidence forward instead of starting from memory.

Try it in one project session. Record one test, then review the note at the next weekly check-in: continue, change the method, or stop that line of work. The point isn’t to document everything—it’s to make the learning usable.