Two different kinds of knowing

Cognitive research has a useful distinction here. Declarative knowledge is knowing that — facts, formulae, definitions. Procedural knowledge is knowing how — the ability to actually do the thing, in conditions that are messy and unfamiliar.

Examinations are efficient at measuring the first and largely blind to the second. So a system optimised for examination performance will, entirely rationally, produce students who are strong on declarative knowledge and untested on procedural. This is not a failure of effort by students or teachers. It is what the incentives select for.

Ask a student to state Ohm's law and most will. Hand them a breadboard, a dead circuit and a multimeter, and something quite different is required.

What only shows up in practice

  • Things fail for boring reasons — a loose connection, a flat battery, a sensor mounted backwards. Debugging is a distinct skill and it is never examined.
  • Measurements carry uncertainty — real data is noisy. Textbook problems supply clean numbers, so students are surprised when reality does not.
  • Assumptions become visible — every formula has conditions attached. You tend to discover them only when you violate one and the result stops making sense.
  • Iteration is normal — a first attempt that does not work is the standard case in real technical work, not evidence of failure.
Knowing that
Declarative — what examinations measure well
Knowing how
Procedural — what work actually requires
Debugging
A core professional skill that is almost never assessed

How we close it

The gap closes in one way: students have to build, measure, fail and try again, with enough support that the failure is instructive rather than discouraging.

  • Every concept paired with something students physically construct or operate
  • Real instruments and real measurement error, rather than idealised numbers
  • Experiments that can genuinely go wrong, with time built in to work out why
  • Simulation used to make invisible mechanisms visible before hands touch hardware
  • Explicitly teaching debugging as a method — isolate, test, narrow down — rather than leaving it to be picked up

Students consistently report the same thing afterwards: the concept they thought they understood turned out to be something they could recite. Working with it changed what they knew.

Read more

The Education–Technology GapAI-Driven TransformationThe Deep-Tech Talent Gap

Turn knowledge into capability

Our sessions are built around building, measuring and troubleshooting. Get in touch to bring one to your students.

Talk to our team