Tech Do – tools don’t change your life—practice does

In Japanese culture, Dō (道) means “the way.” Not a hack. Not a shortcut. A path you walk long enough that it reshapes who you are. It’s the difference between learning a technique and becoming the kind of person who can execute under pressure, stay calm in uncertainty, and improve without needing motivation.

Tech Do is a technological integration of a personal growth path.

Not “Which app should I use?”

But: “What kind of professional am I becoming through the way I use tech?

The core idea

Tech Do is a discipline of deliberate technology use—a personal path where you progressively move from:

• reactive → intentional
• busy → effective
• consuming → creating
• tool-chasing → principle-led systems
• digital chaos → operational clarity

It treats technology like a training ground. Every notification setting, workflow choice, template, automation, or note-taking habit is either building your maturity… or quietly subtracting from it.

What makes it a “Dō” and not a productivity method

A method says: “Do these n steps.”

A Dō says:

• You’re never “done.”
• You’re building character through repetition.
• The point is mastery, not novelty.
• The practice works when life is messy, not when the calendar is empty.

So Tech Do isn’t about becoming a power user.

It’s about becoming the kind of person who can use technology without being used by it.

The promise (and the challenge)

If you commit to Tech Do, you stop asking technology to save you.

You use it to do something harder:

• protect attention
• standardise your best work
• reduce avoidable decisions
• build reliable systems
• strengthen reputation through consistency

And over time, you get what every real “way” delivers:

Not just better output.

A calmer mind. Cleaner execution. Deeper confidence.

The Tech Do Index — a monthly self-assessment

Part one made the case that Tech Do isn’t a productivity method; it’s a way — something you practice, not something you finish. That’s true, and it’s also useless without a way to check your position on the path. A way with no waypoints is just a mood.

This is the waypoint. Not a personality quiz. Not a vibe check. A checklist you sit down with every month, score honestly, and compare against last time.

It works the same whether you’re an individual contributor, a people manager, or an executive. Every item is written to be answered at either scale — “personally, or for those I coordinate.” If you don’t coordinate anyone, you answer for yourself and move on. If you do, you’re accountable for both: what you do, and what you’ve built into how your team works. That second part is where most of the real gaps hide.

How to score it

Twenty-five items across five movements, five items each, plus one trap item per movement that doesn’t count toward your score — it’s there to catch you.

Score every item 0, 1, or 2:

0 — Not present. This doesn’t happen.
1 — Emerging. It happens sometimes, but it isn’t a system yet — you’re relying on willpower or memory, not structure.
2 — Established. It’s a habit or a standard. It would survive a bad week.

Sum the five items in a movement for a score out of 10. Sum all five movements for a score out of 50.

Convert to a band:

0–40% (0–20 points) — Reactive. Technology is setting your terms. 41–70% (21–35 points) — Transitional. Some of this is real, most of it isn’t load-bearing yet.
71–90% (36–45 points) — Intentional. The system holds under normal pressure.
91–100% (46–50 points) — Principle-led. This is how you operate, not what you’re trying to do.

The trap item. After scoring the five real items in a movement, answer the trap honestly — yes or no. If your movement score is 8–10 and the trap is a yes, discount the score. You’re not where the number says. You’ve built something that looks like the outcome without being the outcome, and that’s a more specific failure than just “low score” — it’s worth naming on its own.

If you manage people: on any item, you can score twice — once for what you personally do, once for what you’ve actually built into how your team operates — and take the lower of the two. A strong personal habit that never became a team standard is a gap this test is designed to find, not paper over.

How to use it

Once a month. Not more often — you’re measuring a system, not a mood, and systems don’t move in a few days. What matters is the trend across months, not any single score. A 62% that becomes a 71% next month tells you something. A single 71% tells you almost nothing on its own.

Write the date down when you take it. Compare against your last result before you do anything else with the number.

1. Reactive → Intentional

The question underneath this movement: do you decide when technology gets your attention, or does it decide for you?

1. I have defined windows for checking messages and notifications — personally, or as a standard I’ve set for my team — instead of responding the instant something arrives.
2. Before I open a tool or app, I know why I’m opening it. I’m not opening it out of habit or out of anxiety about missing something.
3. When something interrupts a task, I have a rule for triaging it — personally, or one my team knows and follows — instead of dropping everything by default.
4. I can name the last time I deliberately turned off a notification, alert, or channel — for myself, or a tool I retired for my team — because it wasn’t earning the interruption.
5. My calendar and inbox reflect decisions I made about how I want to work, not just the defaults the tools shipped with.

Trap: I respond fast to almost everything, and it feels like being on top of things. Speed of response isn’t intentional use — reacting quickly to noise is still reacting.

2. Busy → Effective

The question underneath this movement: does your activity produce outcomes, or does it just fill the time available?

1. I can point to a specific outcome my last week of tool use produced — personally, or for the team I coordinate — not just a list of tasks that got touched.
2. I regularly remove a step, a tool, or a recurring meeting — mine or my team’s — because it stopped earning its place, not just add new ones on top.
3. I know the difference between tasks that move something forward and tasks that just keep me occupied, and I can name three of each from this week without having to think hard.
4. When I automate or delegate something, I check afterward whether it actually freed capacity for higher-value work — mine or my team’s — rather than just moving the busywork somewhere else.
5. I have said no to a tool, a project, or a process this month specifically because it added activity without adding outcome.

Trap: my calendar is full and I clear my inbox fast, and that feels like proof I’m effective. A full calendar measures occupation. It doesn’t measure whether any of it mattered.

3. Consuming → Creating

The question underneath this movement: does what you take in turn into something, or does it just accumulate?

1. Information I take in — reports, updates, industry reading — systematically turns into a decision or a directive, mine or one for the team I coordinate, instead of just being read and filed.
2. I have a standard format for turning what I learn into something others can use — a colleague, a team, a client — a playbook, a checklist, a brief — instead of leaving it in my head.
3. When I engage with an external forum, community, or network, something comes out of it — a point of view, a framework — that makes it into my work or my team’s, not just passive networking.
4. Meetings I attend more often produce an output I authored or co-authored — a decision, a document, an assigned owner — than they produce simple alignment.
5. There’s a place where my thinking, or my team’s, accumulates in shareable form — not just scattered notes across four apps.

Trap: I’m visibly active — commenting, reacting, sharing internally or on LinkedIn — and that feels like creating. It isn’t, unless it produces a framework or a decision, mine or my team’s. Reacting to someone else’s idea is still consuming.

4. Tool-chasing → Principle-led

The question underneath this movement: are you choosing tools because they fit a principle, or because they’re new?

1. I can state the principle behind why I use the tools I use — personally, or the ones I’ve standardized for my team — not just “it’s what everyone uses.”
2. When a new tool or AI feature launches, I have a process for deciding whether it fits before I adopt it — mine, or one my team follows — instead of adopting on hype.
3. I have retired a tool because it stopped serving the underlying principle, even though switching cost me time and friction.
4. My workflow would survive losing access to any single tool, because it’s built on a principle, not on that specific product.
5. I could explain my tool stack to someone new in terms of what problem each piece solves, not just what each piece is called.

Trap: I use a lot of tools, and I’m usually trying the newest one before most people have heard of it. Volume of tools tried isn’t a principle-led stack. Being early isn’t the same as being disciplined.

5. Chaos → Clarity

The question underneath this movement: is your operational picture legible, or does it only live in your head — or nowhere at all?

1. If I disappeared for a week, a colleague or my team could find where things stand without asking me, because it’s written down somewhere, not just known by me.
2. I have one place — not four — where the state of my priorities lives, and it’s current, not stale.
3. I can answer “what’s the status of X” in under a minute for my top three priorities, mine or my team’s, without reconstructing it from memory.
4. When something goes wrong, there’s a record of what happened and why — mine or my team’s — not just a memory that will fade in a month.
5. New information — a report, a request, a message — has an obvious place to go, instead of creating a small decision every time about where it belongs.

Trap: I have a lot of systems, folders, and dashboards, and that feels organized. Volume of systems isn’t clarity. More places to look is often more chaos wearing a better outfit.

—

What the score is for

This isn’t a grade.
A 41% on Reactive → Intentional this month and a 58% next month is the entire point — the movement, not the position. Treat any single score as a photograph of a system mid-construction, not a verdict on you.

The trap items matter more than the main score, if you’re honest about them. A high score with a live trap means you’ve optimized for looking like you’re on the path instead of walking it — which, per part one, is the one failure mode a way can’t tolerate. A method can be gamed. A way, by definition, can’t — you’re only cheating yourself out of the thing you said you wanted.

Score it. Date it. Come back in thirty days.