Independent studio · Singapore

Project / 09

Daymark

A calm planning system for focused work.

Category
Concept · Systems
Year
2026
Role
Founder
Status
Fictional concept placeholder
A monochrome weekly planner and pen

Premise

Plan around time.

I wanted to explore a weekly plan that behaves like a quiet instrument instead of a crowded task list.

The concept starts with the week, protects focused blocks, and lets everything else sit around them.

A monochrome weekly planner showing protected work blocks
Concept interface. Fictional placeholder content.

Interaction

A small weekly loop.

Five deliberately simple actions shape the concept interaction.

  1. Plan

    Choose the important block first.

    The Daymark concept week prepared for a focus block
    Editable concept artifact for the planning step.

  2. Reveal

    Surface the next useful action.

  3. Commit

    Record the work without extra ceremony.

  4. Clear

    Finish the block and close the loop.

  5. Reset

    Start again with a clean week.

System

A focus-first model.

This is a conceptual system map, not a production architecture claim.

Week

  • Days
  • Time blocks
  • Notes

Focus

  • Priority
  • Duration
  • State

Review

  • Completed work
  • Open notes
  • Next week
Constraint
Keep the week readable in one view.
Principle
Time is the container, not another field.

Tradeoffs

Every choice removes something.

Every choice removes something.
ConstraintChoiceConsequence
Limited attentionOne focus block per dayDepth over breadth
Decision fatigueDefault time blocksFaster planning with less flexibility
Context switchingNext action stays visibleFewer pivots and more flow
PrivacyLocal-first conceptMore control with more responsibility

Retrospective

What the concept still gets wrong.

Too much editing

The useful rule may be one primary action, not endless arrangement.

Notes can disappear

The memory of the week needs to remain visible without becoming clutter.

Structure can become pressure

A quiet system must also make room for an unplanned day.

Code evidence

The focus rule in plain language.

chooseFocus(day)
  keep one important block
  place smaller work around it
  leave space for change
  review before carrying work forward
Illustrative pseudocode for this fictional concept. It is not production source code.

Still unresolved

Questions worth keeping open.

Boundaries

Can the tool stay small as more needs appear?

Planning versus doing

How little planning is enough to support action?

Review discipline

How can reflection remain useful when a week gets busy?