01 / Context
Why this project exists
SPMP was built for a concrete personal need: keep a multi-year set of academic and application obligations visible enough to act on. The spreadsheet turned broad goals into trackable categories, dates, and next actions.
Unlike a one-time checklist, the system was intended to be followed over time. Its usefulness depended on being easy to update and clear enough to show where attention was needed.
02 / Approach
How the problem was framed
Excel provided a flexible environment for structuring information without building a full application. The project used tables and planning logic to gather requirements, progress, and application-related work in one place.
The system was personal, so it could evolve with experience. Fields and views could be adjusted when the original organization stopped matching reality - a practical lesson in designing tools around the actual user rather than an imagined workflow.
03 / Result
What exists now
The workbook supported the creator's high-school planning and is retained as an archive project. The original documentation is limited, and private academic information is not published on this site.
Its significance is methodological: before later engineering programs and software experiments, SPMP practiced decomposition, tracking, feedback, and steady execution using an accessible tool.
04 / Reflection
Lessons and next steps
A planning system is valuable only when it changes behavior. Low-friction updates and visible next actions matter more than elaborate formatting.
If recreated today, the focus would be a smaller set of decision-oriented views, clearer separation between goals and tasks, and careful handling of personal data.
- Scope and claims are limited to what the surviving project record supports.
- Future updates will add verified media, measurements, and milestones as they become available.