Category: 2026

Posted on by — Leave a comment

Why Simple Systems Beat Complex Tools for Personal Projects

When a personal project starts to feel messy or unmanageable, the instinctive response is often to look for a better tool. It becomes a case of simple systems vs complex tools, and how they can be applied properly.

This may include:

A new app.
A more powerful platform.
A more sophisticated workflow.
Managing personal projects.

I’ve done this more times than I can count. And while tools can help, I’ve learned – sometimes the hard way – that most struggling projects don’t fail because the tools are inadequate.

They fail because the system around the tools is missing or unclear.

In my experience, the real difference between stalled and sustainable personal projects is almost always the system – not the tool.

This post explains why simple systems consistently outperform complex tools in personal projects, and how shifting your focus away from optimisation and towards structure can dramatically improve follow-through and create simple workflows.

Simple Systems vs Complex Tools – Why Tools Feel Productive but Systems Create Real Progress

Tools are tangible. They promise leverage, efficiency, and clarity. Installing or configuring one feels like progress, even when nothing meaningful has changed.

Systems are quieter.

A system doesn’t announce itself. It doesn’t look impressive. But it defines:

  • when work happens
  • what happens next
  • how decisions are made
  • when a project pauses or ends

Tools assist execution. Systems govern behaviour.

Without a system, even the best tool becomes a distraction.

Why Productivity Tools Are So Tempting in Personal Projects

There’s a psychological reason tools are so appealing.

Choosing a tool:

  • is a finite decision
  • provides immediate feedback
  • avoids confronting deeper problems

It’s far easier to spend an afternoon setting up software than to define:

  • realistic constraints
  • success criteria
  • stopping conditions

Tools let you feel productive without forcing commitment.

Systems do the opposite – they expose ambiguity.

What a System Is (and Why It’s Not Just Another Tool)

A system is not:

  • a checklist
  • a productivity app
  • a rigid schedule

A system is:

  • a repeatable pattern
  • a decision framework
  • a defined flow from start to finish

At its simplest, a system answers three questions:

  1. When does this happen?
  2. What is the next concrete action?
  3. When do I stop or reassess?

Once those are defined, tools become optional.

How Complex Tools Cause Friction in Personal Projects

Complex tools tend to introduce:

  • configuration overhead
  • maintenance requirements
  • cognitive load
  • dependency on motivation

They assume consistent energy, focus, and interest – which personal projects rarely have.

When energy dips, the tool becomes friction instead of leverage. Miss a few days, and the system collapses because there wasn’t one.

This is why people repeatedly abandon:

  • task managers
  • note systems
  • project trackers

Not because they’re bad – but because they demand more structure than the project actually has.

Why Simple Systems Scale Better Than Complex Tools

Personal projects live in unstable environments:

  • changing priorities
  • limited time
  • emotional investment
  • external interruptions

Simple systems survive these conditions because they are:

  • easy to resume
  • forgiving of missed days
  • clear about next steps

A system that works at 50% consistency is more valuable than a tool that only works at 90%.

Build the System First, Choose the Tool Second

Instead of starting with a tool, start by defining the system in plain language.

For example:

  • “I work on this project twice a week.”
  • “Each session has one clearly defined task.”
  • “If I miss a session, I resume at the next scheduled time.”
  • “Every four weeks, I decide whether to continue or stop.”

Only after this exists does it make sense to choose a tool – and often, pen and paper is sufficient.

The system does the heavy lifting. The tool just records it.

This same systems-first thinking has shaped how I approach daily routines and long-running projects elsewhere on this site.

Why Systems Matter in Both Technical and Non-Technical Projects

This pattern shows up everywhere:

  • writing
  • learning
  • side projects
  • technical builds
  • creative work

In technical contexts, the temptation is even stronger because tools feel inherently productive.

But complexity compounds quickly. Without a governing system, tools multiply, workflows fragment, and momentum disappears.

The more complex the tools, the more important the system becomes.

When Tools Actually Matter (After the System Exists)

This isn’t an argument against tools entirely.

Tools matter when:

  • the system is already clear
  • scale demands automation
  • coordination across people is required

At that point, tools amplify a system that already works.

Used prematurely, they only amplify confusion.

The Long-Term Advantage of Boring, Simple Systems

Simple systems don’t generate excitement. They don’t look impressive. They don’t inspire screenshots or tutorials.

What they do is:

  • reduce decision fatigue
  • make progress predictable
  • lower emotional resistance
  • keep projects alive longer

That last point is critical.

Most personal projects don’t fail because they’re impossible. They fail because they slowly dissolve under friction.

Systems slow that decay.

Final Thoughts

If a project feels stuck, the answer is rarely “find a better tool”.

More often, the real question is:

What system is this project actually running on?

When you define the system clearly – even in imperfect, human terms – tools become optional, interchangeable, and far less important.

Progress follows structure, not sophistication. This is truly a case of simple systems vs complex tools, and the roles they play.

RELATED ARTICLE:

Posted on by — Leave a comment

How I Reduced Decision Fatigue in the Morning With Simple Systems

Decision fatigue in the morning used to drain far more energy than they should have.

Nothing was technically “wrong”. There was no single crisis, no dramatic failure. But by the time the day had properly started, I already felt behind – mentally tired, impatient, and strangely scattered.

The issue wasn’t lack of motivation or discipline. It was the sheer number of small decisions stacked tightly together before breakfast.

Over time, I came to understand that what I was experiencing wasn’t laziness or poor planning. It was decision fatigue – and the solution wasn’t trying harder. It was building simple systems that removed decisions entirely.

This post outlines how we have reduced morning decision fatigue by designing predictable, low-friction systems that work even on low-energy days.

What Decision Fatigue in the Morning Actually Looks Like at Home

Decision fatigue at home isn’t dramatic. It’s subtle.

It shows up as:

  • irritation over small things
  • procrastination on simple tasks
  • feeling rushed even when time is available
  • snapping decisions instead of thoughtful ones

In the morning, decisions pile up fast:

  • what to wear
  • what to eat
  • what to pack
  • what order to do things in
  • what can be skipped

Individually, none of these are difficult. Collectively, they consume mental bandwidth before the day has even begun.

The mistake I made for years was assuming the problem was willpower. In reality, the problem was exposure – too many choices, too early, every single day.

Why Motivation Fails and Systems Don’t

Motivation is inconsistent by nature. It fluctuates with sleep, stress, health, and mood.

Systems, on the other hand, are indifferent.

A system doesn’t care whether you feel inspired, tired, or distracted. It simply runs – provided it’s designed simply enough.

Once I stopped trying to “be better in the mornings” and instead focused on designing mornings that required less of me mentally, things changed quickly.

This shift in mindset was the turning point:

Don’t rely on good decisions. Remove the need for decisions.

System One: Remove Repetitive Decisions Entirely

The fastest way to reduce decision fatigue is to eliminate repeat decisions. Simplify the daily routines.

Anything that happens daily is a candidate.

Examples:

  • fixed breakfast options
  • predefined lunch components
  • limited clothing combinations
  • consistent morning order

Instead of asking “What should I do?”, the system answers automatically.

This doesn’t remove flexibility – it contains it. Variety exists across the week, not inside every single morning.

This same approach later became the basis for how we handle school lunches, because the underlying problem was identical: too many small decisions under time pressure.

System Two: Sequence Tasks the Same Way Every Day

Order matters more than speed.

By doing tasks in the same sequence every morning as a routine system, the brain stops negotiating. There’s no debate about what comes next – momentum takes over.

A predictable order:

  • reduces context switching
  • lowers anxiety
  • makes omissions obvious

When something is missing, it stands out immediately because the sequence is broken.

The goal isn’t to optimise for speed. It’s to optimise for flow.

System Three: Batch Similar Actions Together

Batching is a simple concept borrowed from production environments and professional kitchens.

Instead of completing one full task at a time, you:

  • repeat the same action across multiple items
  • then move to the next action

At home, this might mean:

  • preparing all food components together
  • laying out everything before assembling
  • grouping similar tasks instead of jumping between them

Batching reduces mental resets – one of the biggest hidden energy drains in the morning.

System Four: Use Visual Cues Instead of Memory

Memory is unreliable under pressure.

Visual systems are not.

Instead of relying on mental checklists, we started using:

  • physical layouts
  • visible staging areas
  • consistent placement of items

When something is missing, it’s immediately obvious – no mental recall required.

This is especially important when mornings involve other people, interruptions, or changing timelines.

What These Systems Don’t Solve (And That’s Fine)

These systems don’t:

  • eliminate all stress
  • prevent every bad morning
  • guarantee calm children or perfect routines

What they do is reduce the baseline load.

By starting the day with fewer decisions, you preserve mental energy for things that actually require thought, patience, or emotional regulation.

That trade-off is worth it.

Why This Works Beyond Mornings

The biggest surprise was how transferable this thinking became.

Once you learn to spot decision fatigue in one area, you start seeing it everywhere:

  • personal projects
  • technical work
  • planning
  • even rest

The principle is always the same:

Wherever decisions repeat, systems belong.

Final Thoughts

Decision fatigue isn’t a personal failing. It’s a design problem.

When mornings feel harder than they should, the solution isn’t more motivation or stricter discipline. It’s fewer decisions – and systems that quietly carry the load for you.

You don’t need perfect mornings.

You need mornings that work even when you’re not at your best. Reducing the mental load just makes this easier.

RELATED ARTICLE:

Posted on by — Leave a comment

How I Pack School Lunches for Four Kids Without Losing My Mind

Mornings are already busy. Packing school lunches for four kids on top of everything else can easily turn a calm start into controlled chaos.

For a long time, I approached the school lunch routine reactively – deciding what to make on the fly, negotiating preferences, and constantly feeling behind before the day had even properly started. The problem wasn’t effort. It was decision overload, repetition, and lack of structure.

Over time, I realised that packing school lunches isn’t really a food problem. It’s a systems problem.

This post outlines the school lunch routine I now use to pack lunches for four kids efficiently, sequentially, and with far less stress. It’s not perfect, but it’s sustainable – and that matters far more on weekday mornings.

Why Packing School Lunches for Four Kids Is So Stressful

The difficulty isn’t just the number of lunches. It’s the stacking of constraints:

  • limited morning time
  • different food preferences
  • school rules and restrictions
  • nutritional expectations
  • shrinking patience as the clock ticks

Each decision pulls a little more mental energy. By the third or fourth lunch, fatigue sets in and mistakes creep in – forgotten items, rushed choices, or unnecessary arguments.

What finally helped was treating lunch prep the same way I treat other recurring tasks: by designing a process that removes decisions wherever possible.

This same systems-first thinking has helped me in other areas of life as well, from technical projects to daily routines.

Reduce Morning Decisions When Packing School Lunches

The single biggest improvement came from moving decisions out of the morning entirely.

Instead of asking “what should I pack today?”, I created a small, repeatable set of lunch components that rotate predictably. This greatly reduced the chance of decision fatigue in the morning.

Each lunch is built from the same categories:

  • main item
  • snack
  • fruit or vegetable
  • optional extras

The options inside each category are fixed for the week. This means the only “decision” in the morning is assembly, not creativity.

When there are fewer choices, everything moves faster.

Use the Same Containers for Every School Lunch

Containers matter more than most people realise.

When every lunch uses the same container type:

  • portions become automatic
  • packing order becomes muscle memory
  • cleanup is simpler
  • visual checks are faster

Each child has:

  • one main lunch container
  • one snack container
  • one drink bottle

Nothing fancy. The consistency removes friction.

I don’t need to think about whether something fits – if it’s on the list, it fits by default.

Pack School Lunches Sequentially to Save Time

This was a surprisingly big win.

Instead of packing one full lunch at a time, I pack the same component for all four lunches in sequence.

For example:

  1. add the main item to all four containers
  2. add fruit or vegetables to all four
  3. add snacks to all four
  4. final check and close

This batching approach:

  • reduces context switching
  • prevents missed items
  • speeds everything up

It’s the same principle used in manufacturing and professional kitchens – and it works just as well at home.

Focus on Consistent, Realistic School Lunch Nutrition

One of the biggest mental traps with school lunches is aiming for perfection.

Balanced nutrition matters, but consistency matters more.

Rather than trying to reinvent healthy lunches every day, I focus on:

  • reasonable variety across the week
  • predictable structure
  • foods the kids will actually eat

A lunch that comes home untouched helps no one. Some of it may go to the chooks as scraps, but that doesn’t help the growing humans on the day.

By removing the pressure to be creative or impressive, the process becomes calmer – and ironically, more sustainable long term.

Prepare School Lunch Components the Night Before

Anything that can be done outside the morning rush should be.

Helpful examples:

  • washing fruit the night before
  • pre-portioning snacks for the week
  • keeping lunch components in one dedicated fridge area
  • refilling drink bottles immediately after school

This turns mornings into assembly, not preparation.

Even saving five minutes makes a noticeable difference when four kids are involved.

Use Visual Checks to Avoid Forgotten Lunch Items

Mental checklists fail under pressure.

Visual systems don’t.

Before finishing, I do a quick scan:

  • one container per child
  • one drink bottle per child
  • lunch bags lined up in order

If something looks wrong, it’s immediately obvious.

This removes the need to remember whether everything was packed.

What This System Doesn’t Do (and That’s OK)

This system:

  • doesn’t guarantee kids will love every lunch
  • doesn’t eliminate all complaints
  • doesn’t aim for novelty

What it does do:

  • reduce stress
  • reduce decision fatigue
  • make mornings calmer
  • free mental energy for more important things

That trade-off is worth it.

Why Systems Beat Motivation in Busy Family Mornings

Most lunch-packing advice focuses on motivation, inspiration, or creativity.

In reality, mornings fail because motivation fluctuates, but systems don’t.

By designing a process that works even on low-energy days, you protect yourself from burnout – and create consistency for your kids at the same time.

Final Thoughts

Packing school lunches for four kids will never be effortless. But it doesn’t need to be exhausting either.

Once I stopped treating lunches as a daily problem to solve, and started treating them as a system to run, everything changed. Mornings became quieter, faster, and far less emotionally charged.

If you’re currently dreading lunch prep each day, don’t aim to do it better.

Aim to do it with fewer decisions.

That alone makes all the difference.

Posted on by — Leave a comment

Building a Moon Planting System for the Southern Hemisphere

Moon planting in the Southern Hemisphere is one of those practices that sits at the intersection of tradition, observation, and personal experimentation. It’s widely referenced, frequently debated, and often presented as a fixed set of rules.

What I found, however, was that most moon planting guidance is either:

  • written with the Northern Hemisphere in mind, or
  • fragmented across charts, blogs, and almanacs, or
  • too vague to be used consistently in day-to-day planning

This project didn’t start as an attempt to “prove” or “disprove” moon planting. It started as a much simpler problem:

I wanted a structured, Southern Hemisphere-appropriate way to plan gardening activities without constantly researching the same information.

So instead of bookmarking advice, I decided to build a small system.

The Problem With Advice for Moon Planting in the Southern Hemisphere

Moon planting is often presented as universal, but most practical guides quietly assume:

  • Northern Hemisphere seasons
  • temperate climates
  • static month-to-season relationships

For gardeners in the Southern Hemisphere, especially in regions like Australia, this creates friction.

You’ll often see advice that:

  • references “spring” without clarifying hemisphere
  • aligns planting suggestions to months that don’t match local seasons
  • mixes lunar phases with climate assumptions that simply don’t apply

None of this makes the practice unusable – but it does make it hard to rely on without constant interpretation.

Over time, that interpretation cost more mental effort than it was worth.

Why I Built a Moon Planting System Instead of Following a Guide

I didn’t want:

  • a single printable chart
  • a generic calendar graphic
  • another set of rules to memorise

What I wanted was:

  • something location-aware
  • something repeatable year to year
  • something that separated data from decisions

In other words, I wanted a system that could:

  • tell me what phase the moon is in
  • align that phase to a Southern Hemisphere context
  • let me decide what to do with that information

This is consistent with how I approach most long-running projects:
build structure first, interpretation second.

How the Moon Planting System Is Structured for the Southern Hemisphere

At its core, the system is intentionally simple.

It separates the project into a few distinct layers:

1. Time and Location Data

  • Year-specific moon phase dates
  • Southern Hemisphere season alignment
  • Regional climate assumptions (broad, not hyper-local)

This avoids hard-coding advice into fixed months.

2. Phase Classification

Each lunar phase is treated as a planning signal, not a command.

For example:

  • new moon periods are associated with preparation and planning
  • waxing phases align with above-ground growth activities
  • waning phases suggest maintenance or root-focused work

These associations are descriptive, not prescriptive.

3. Interpretation Layer

This is where flexibility lives.

The system doesn’t tell you what you must plant.
It gives you a consistent framework you can interpret alongside:

  • weather forecasts
  • soil conditions
  • plant varieties
  • personal timing constraints

That separation is deliberate.

What the Moon Planting System Does – and What It Doesn’t

This project is designed to support planning, not outcomes.

What it does:

  • provides a structured view of lunar phases
  • aligns them correctly for the Southern Hemisphere
  • reduces repeated research and decision fatigue
  • creates consistency across seasons and years

What it doesn’t do:

  • guarantee plant health or yield
  • override climate, soil, or care practices
  • replace observation or experience
  • claim scientific certainty

Moon planting, like many traditional practices, works best when treated as one input among many, not a rulebook.

Lessons Learned While Building the Moon Planting System

A few things became clear as this project evolved:

  • Local context matters more than theory
    Even within the Southern Hemisphere, climate differences are significant.
  • Rigid rules don’t scale
    Any system that demands strict adherence quickly breaks down in real life.
  • Structure reduces cognitive load
    Having the information organised removes the mental friction of constantly re-checking sources.
  • Simplicity survives longer
    The less the system tries to “decide for you,” the more useful it remains.

These lessons mirror patterns I’ve seen in completely unrelated projects – from technical systems to everyday routines.

How This Fits Into My Broader Approach

This moon planting project sits comfortably alongside other work I’ve documented here.

The common thread isn’t gardening. It’s systems thinking:

  • building frameworks that work under imperfect conditions
  • reducing unnecessary decisions
  • creating tools that support consistency rather than optimisation

Whether it’s planning a garden, managing a project, or structuring a routine, the goal is the same:

build something simple enough to keep using.

Where the Project Is Headed

At the moment, this system is primarily for personal use.

Possible future directions include:

  • expanding datasets to cover multiple Australian regions
  • refining seasonal assumptions for different climates
  • keeping it as a private planning tool rather than a public guide

There’s no rush to turn it into anything more than it needs to be.
That restraint is intentional.

Final Thoughts

The moon planting in the southern hemisphere project wasn’t about validating a belief or creating a definitive guide. It was about solving a practical problem:

How do I organise scattered information into something I can actually use?

Moon planting provided the context, but the real outcome was a reusable system – one that reduces friction, respects local conditions, and leaves room for judgement.

That, more than any specific planting recommendation, is what made the project worthwhile.

Image showing the dashboard of the Moon Planting in the Southern Hemisphere. Moon gardening in Australia 2026.
Image showing the plant dictionary of the Moon Garden Project. Moon gardening in Australia 2026.
Image showing a journal entry of the Moon Garden Project. Moon gardening in Australia 2026.
Image showing the visual calendar of the Moon Planting in the Southern Hemisphere. Moon gardening in Australia 2026.

If you would like to try out the Moon Garden Project, you can do so by navigating to the following link:
https://jaysndees.com.au/moon/index.html

Bookmark the link, install the app by using the icon that will appear beside the URL bar, enable the notifications (and allow them too if requested), and you will have your very own, self sufficient Moon Gardening reference!

If you have any questions, suggestions, comments, or feedback, please use our Contact Us form .

Good luck, and many happy moon gardening in Australia 2026 adventures!

This post documents a personal project, not gardening advice.

RELATED ARTICLES: