The guaranteed, “no stress” way to remember to get your regular systems DONE. This small tweak made all the difference.
Nov 12, 2021
One critical aspect of making systems work well is having some way of triggering regular systems.
I have tried using tracking boards for this, but it just was far too easy NOT to look.
It might have been great if I used the board…
But the simple fact was that I did not.
People, including me, default to the path of least resistance.
The solution?
Set up repeating events in my calendar.
At least I look at my calendar semi-regularly ;)
Yet even this was not enough!!
The notification would come and I would dismiss it.
I would tell myself I would remember to do it later.
I frequently did not.
The real trick was to ensure that the calendar sent an EMAIL about the recurring work.
This way, the email comes into my email inbox and must be dealt with - i.e. it acts as the starters’ gun to duplicate and execute the required system.
Question for you: how do you trigger the repeating systems that must be done in your business?
To your success,
Tom
PS. By the way, I set up a systems skillset assessment so you can know where you score on your systems skills… you can take it here - https://www.systemio.dev/skillsets-assessment
Recent Posts
MagicBoards Blogs
All Categories adapter contracts ai & automation ai production ai results ai route security ai system design ai workflow ai-systems architecture architecture reference artifact contracts artifact freshness artifact migrations artifact validation assign work async navigation async ui audit and review audit review audit verdicts audit-driven rework auth boundary authority boundaries authority domains automation reliability branch governance business systems business systems. change management change-management ci governance ci/cd cli contracts cli preflight cli progress cli ux cli wrapper code cleanup code-review component migration concurrency confirmation dialogs constraints correction loop data identity data integrity database transactions database-migrations date placement date-sensitive ui decision records decision-making dependency-aware testing dependency-management dependency-security deployment design design contract deterministic diagnostics deterministic fallback developer experience diagnostics digital marketing dispatch authority dispatch boundaries documentation documentation governance documentation truth duplicate prevention durable evidence durable state durable tokens editing editor guidance engineering process engineering standards environment variables evidence evidence-gating external state fail closed fail-closed behavior fail-closed parsing fail-closed validation failure reporting feedback artifact filtering predicates framework upgrades funnel builds funnels gate design git worktrees governance governed pauses governed workflows hormozi human gates human review identity reconciliation identity reservation instrumentation interface contracts invariants key rotation knowledge management legacy code lifecycle boundaries lifecycle facade lifecycle management lifecycle outcomes lifecycle state linting loading states lockfiles locking magicboard magicboards measurement minimum viable parenting move and copy paths mutation safety no-call tests normalization npm-audit observability operator experience operator recovery organisation output contracts output validation ownership-proved rollback paid api protection parallel execution parser validation path validation pending state people performance planned period pre-mutation guards privacy process process boundaries processes producer contracts product ux production boundary productivity productivity tips project completion project management project tracking prompt contracts prompt guardrails provenance public routes quality gates read-only contracts reference documents regression protection release promotion release-management remote verification render ownership reproducible-builds retired behavior retry vs rework review findings review gates risk risk-management role mapping route contracts runtime logging runtime provenance safe-by-default ui safety boundaries scaling schema validation scope control scope-control secret detection security security hardening security policy security review semantic verification shared ownership shared types side-effect surfaces software software-architecture sop stale request handling state-management status composition strategic dashboard structured output subprocesses system system design systems team collaboration technical debt template testing testing and verification toolchain tooling tracking transition continuity ux safety validation verdict contracts verification verification scope version history visual acceptance visual coherence website development work worker contracts workflow workflow design workflow governance workflow optimization worktree isolation