TSSP™ — Time Segmented Sub Projects™ Dr. UVC Insights™ Post 556_5/20/26 Wed 10pm
===
Dr. UVC Insights™ Post 556_5/20/26 Wed 10pm
====
TSSP™ — Time Segmented Sub Projects™
How I Keep Five Parallel Projects Moving Without Breaking Down
I am running five projects in parallel right now.
UVCMI 777™ platform — July 1 launch, 42 days out.
Dr. UVC Market Insights™ — Sub stack campaign, 3 posts a day minimum.
50 publications — math primers, apps, e books, books — target Dec 2027.
AI Solvability Tests — separate research stream.
Pink Book — journal canon, ongoing capture.
Any one of these is a full-time project.
Running all five simultaneously is the reality.
Some days the cognitive load hits and everything stalls. Not from lack of ideas. Not from lack of work. From the weight of the whole picture sitting on top of every individual task.
That is the problem I solved — by accident, through doing. I call it TSSP™. Time Segmented Sub Projects™.
What did not work
I tried standard approaches. Everyone does.
Work Breakdown Structure — great for knowing what all the pieces are. Useless for knowing what to do on a Tuesday afternoon when energy is low.
Pomodoro — 25 minutes of work, 5 minute break. Fine for a single defined task. Useless when the task itself is undefined or too large. You spend the 25 minutes figuring out where to start.
Agile Sprints — built for teams, weeks-long windows. Does not solve the friction of one person, one morning, five live projects.
All three tell you something about the work. None of them tell you how to get traction on a hard day.
What I discovered by doing
I did not sit down and design TSSP™. I noticed I was already running it.
Every session I run has a timestamp and a scope. Every session closes with a PDF — something that exists and is filed when the session ends. Sessions run 30 minutes to 90 minutes. Not 6-hour marathons. Not 5-minute checks. Each session belongs to one project. No cross-pollination.
That pattern — already operating before I named it — is TSSP™.
A task is not ready for execution until it is small enough to understand at a glance and bound by a time limit short enough to prevent procrastination.
That is the whole principle. Everything else is implementation detail.
The five elements of every TSSP™
Every Time Segmented Sub Project™ has five things. No exceptions.
1. Identifier — a name and timestamp. Not vague. Specific.
Bad: “Work on platform.”
Good: “052026-wed-UVCMI — architecture spec, Screen 2 logic rules.”
2. Type — what kind of work is this session doing?
Architecture walkthrough. Market read. Spec capture. Empirical validation. Strategic decision. Post draft. Cowork directive. Naming the type sets expectations before the session starts.
3. Scope — exactly what is in bounds. And what is not.
If I am documenting backend logic, the UX files stay closed. Scope protection is the discipline that makes the chunk actually small.
4. Time budget — strict, predetermined, honored.
30 minutes. 45 minutes. 90 minutes. Not “until it is done.” Done is defined by the timer, not the task.
5. Output — what physically exists when the timer rings?
A PDF. A draft. A decision recorded. A spec section written. If there is no defined output, it is not a TSSP™. It is a drift session.
How it plays out in practice
Building UVCMI 777™ is the canonical example.
The platform touches market engine design, UX architecture, backend spec, Substack campaign, trademark roadmap, beta access, subscriber tiering. Trying to hold all of it in one session is the recipe for producing nothing.
TSSP™ discipline: each session touches one thing.
Tuesday morning: master tracker universe categorization. Output: universe map + HTML block.
Tuesday afternoon: Post 1 draft. Output: .docx + .txt.
Tuesday evening: footer verified URLs. Output: master footer block.
Each session produced something real. Nothing bled into the next session’s scope. By end of day, three separate workstreams moved forward.
The 50-publication goal is where TSSP™ becomes essential.
50 math primers, apps, ebooks, and books by end of 2027. That is 19 months from now.
Each publication = 5 TSSPs. Outline (1) + Draft (2) + Edit (1) + Publish (1).
50 publications × 5 TSSPs = 250 total TSSPs.
250 TSSPs over 19 months = 13 per month = 3 per week.
3 focused sessions per week over 19 months. That is the entire 50-publication goal, chunked.
The overwhelming number disappears. What remains is a cadence.
The one rule that covers everything
If I had to reduce TSSP™ to a single operating rule:
Never start a session without knowing what will exist when it ends.
Not a feeling of progress. Not “I worked on it.” Something that physically exists and is filed.
That output guarantee is what separates a TSSP™ from time spent. On low-energy days the bar is not “do brilliant work.” The bar is “produce the defined output.”
Achievable consistently beats brilliant occasionally.
What TSSP™ is not
Not a replacement for deep work. Some problems need long uninterrupted blocks. Protect those separately.
Not a way to avoid hard things. If a task feels overwhelming because it is genuinely hard, chunking it can become a way to feel productive while avoiding the core. Check that occasionally.
Not a team methodology. WBS, Sprints, Scrum — those scale to teams. TSSP™ is a solo practitioner’s method. One person. Multiple projects. Cognitive load managed.
Why I am sharing this
I have been posting market analysis for over a year. 555posts before this campaign. Unmonetized. Every one produced.
People ask how I keep the output consistent. Part of the answer is the engine — UVCMI 777™, the reads, the tracker discipline. Part of the answer is this: TSSP™.
The method is not complicated. It is repeatable. And repeatable beats complicated every time.
If you are running parallel projects and some days the load hits — try it. Name the session. Set the clock. Define the output. See what happens when the bar is “this one small thing” instead of “the whole project.”
===========
Dr. UV™
Founder, Dr. UVC LLC · Dr. UVC AI LLC
Dr. UVC Market Insights™ — launching July 1, 2026
Every asset, every timeframe, one consistent UVC Lens™.
====
Post # 556
====