CURRENT
Begin messy. Finish with a system people can keep.
Early conversation is allowed to be incomplete. The published software is not. We move a brief from scattered needs to a defined scope, then to a platform that staff can run.
-
Listen for the actual constraint
Teaching hours, staff capacity, policy, existing records. The first useful output is a short list of what must remain true.
-
Write the scope as a boundary
What is in, what is later, what is refused. Custom programming and platform work both need this line, or the product will sprawl.
-
Build the current surface
Learning platforms, student systems or advisory — whichever the brief named — implemented so it can be demonstrated against the constraint.
-
Hand over something operable
Cloud education, administration and the knowledge to keep the system after we leave. Consulting continues only where it is still useful.
The finished state is quiet. The earlier state is allowed to be restless. Only the first is shipped.
What we need from you.
A named programme or operational problem. Who teaches and who administers. Any systems that must remain. A sense of what “working” would look like in the first term of use.