Forte & Francesco RTO Tool Selection Method

Last updated: 12 July 2026

Select, trial, and lock in the right productivity tool stack for your current life phase without wasted migrations, shiny-object switching, or over-engineered systems.

// TL;DR

The Forte & Francesco RTO Tool Selection Method is a framework for choosing, trialing, and committing to the right productivity tools for your current life phase — without wasted migrations or shiny-object switching. RTO stands for Research (define Must-Haves, shortlist three apps), Trial (a forced 90-day single-project test with weekly journaling), and Optimize (align the tool to your role for maximum longevity). Use it whenever you feel real friction with your stack, enter a new career or life phase (roughly every 3-5 years, or 2-3 with AI), or want to audit an over-complex system. Skip it if you're just chasing novelty.

Framework

// When should you use the RTO tool selection method?

Use this skill whenever you are considering adopting a new productivity app, feeling friction with your current stack, or entering a new career or life phase (roughly every 3-5 years). Also use it to audit an existing stack that has grown too complex.

// What do you need before running the RTO Method?

Current Stackrequired
List every productivity app you currently use: task manager, note-taking app, calendar, email, and any AI tools.
Life/Work Phaserequired
Briefly describe your current role, responsibilities, and any recent life changes (new job, new family situation, new project type) that may have shifted your needs.
Pain Pointsrequired
What is not working in your current stack? What tasks feel like unnecessary administration? What is missing?
Must-Haves vs. Can-Live-Withoutsrequired
List the non-negotiable features your tool(s) must have, and the features you are willing to sacrifice for simplicity or integration.
Candidate Apps
Optional short list of apps you are already considering. Leave blank if starting from scratch.

// What are the core principles behind the RTO Method?

The 3-to-5-Year Cycle

People naturally outgrow their productivity stack every 3-5 years as their career and life circumstances shift. AI is compressing this to roughly 2-3 years. Recognising you are in a cycle transition is the trigger to run the RTO method — not boredom or hype.

Must-Haves vs. Can-Live-Withouts

Before evaluating any app, define your non-negotiable requirements separately from your nice-to-haves. All-in-one workspaces typically deliver an 80% experience across many functions; knowing which 20% you cannot compromise on determines whether an all-in-one is viable or whether you need a best-in-class specialist app.

Moving House Analogy

Switching a note-taking app is like moving house — expensive in time, effort, and stress. Switching a to-do list app is like moving car. Switching a calendar app is like switching phones — easiest of all. Migrate as infrequently as possible, and when you do, match your migration effort to the category's true switching cost.

The Starter Kit (Tasks + Notes + Calendar)

Every beginner stack needs exactly three core tools: a task manager, a note-taking app, and a calendar. Everything else is a bonus. Start with native platform defaults (Apple or Google ecosystem) before graduating to third-party apps. Two to three apps is the right starting ceiling.

Admin → Decision-Making & Creativity Split

Roughly 40% of a typical knowledge worker's day is administrative clerical work. AI is absorbing that layer. What remains — and what productivity tools must serve — is the quality of your decision-making and the quality of your creativity. Design your stack around those two outputs, not around managing overload.

Admin, Efficiency, Errands (AI Value Ladder)

AI is delivering real value in productivity in three ascending layers: (1) Administration — auto-tagging, auto-sorting, auto-scheduling; (2) Efficiency — intelligent task allocation and workload structuring; (3) Errands — micro-actions executed on your behalf in the background. Evaluate any AI productivity claim against which of these three layers it actually operates in.

Keep It Dumb and Simple

A system that is more to manage than to get things done has failed. If you find yourself maintaining your productivity system more than using it to produce real work, strip it back immediately. Complexity is not sophistication.

// How do you apply the RTO Method step by step?

1
Diagnose your current phase and trigger
Ask: has your role, family situation, or primary project type changed in the last 6-12 months? If yes, you are likely in a 3-to-5-year cycle transition. Do not run RTO out of boredom or because a new app went viral. Only proceed if you have genuine unmet needs or real pain in your current stack.
2
Define your Must-Haves vs. Can-Live-Withouts
Write two explicit lists before looking at any app. Must-Haves are deal-breakers — the absence of these ends the trial. Can-Live-Withouts are features you would like but will sacrifice for simplicity or integration. Be specific: 'offline access', 'recurring task support', 'calendar two-way sync'. Vague requirements produce bad selections.
3
Identify which of the three core categories you are solving for
Use the Starter Kit lens: Tasks, Notes, Calendar. Determine whether you need a specialist best-in-class app for each category or whether an all-in-one workspace covers your Must-Haves at 80% quality. If your Must-Haves are concentrated in one category (e.g., calendar hyper-features), keep that category as a standalone specialist and allow compromise elsewhere.
4
Research and build a shortlist of exactly three candidates
This is the R of RTO. Go deep enough that you can rank your three options 1, 2, 3. Number 1 is your primary trial candidate; 2 and 3 are your fallbacks. Use independent reviewers, category-specific comparison sites, and community feedback — not just the app's own marketing. Check company roadmaps to see if missing features are incoming.
5
Run a forced 90-day trial on your top candidate
This is the T of RTO. Before starting, ask yourself: 'Am I genuinely willing to spend 90 days with this app and invest the migration effort?' If you are already umming and ahing, go back to Research — your shortlist is not solid enough. Do NOT migrate everything. Migrate one single project — ideally an active one — and run it from start to finish inside the new tool. This surfaces day-to-day friction without the disaster of a full migration you may need to undo.
6
Keep a weekly trial journal throughout the 90 days
Each week, note: (a) what worked well, (b) what did not work, (c) whether missing features appear on the roadmap. This journal becomes your evidence base. At day 90, you either continue (the app passes) or you have a documented list of refined Must-Haves to use in your next Research pass. You will rarely need to run RTO more than twice if you did Research thoroughly.
7
Optimise by aligning the tool to your specific role and industry
This is the O of RTO. Find how people in your exact role or industry use the tool. Learn every feature relevant to your Must-Haves. The goal is to stay in this tool as long as possible — treat optimisation as moving into a house and making it yours, not as continuous tinkering. Resist re-opening the tool-selection question until the next genuine life/work phase transition.
8
Audit your stack for AI value — Admin, Efficiency, or Errands?
For each tool in your finalised stack, ask: does it remove administration (auto-tagging, auto-scheduling)? Does it improve efficiency (intelligent workload allocation, smart frames)? Does it handle errands (background micro-actions)? Remove or deprioritise AI features that are pure hype and do not map to one of these three layers. Prioritise features that have already crossed into reliable daily use.
9
Decide your migration depth using the Projects-Areas-Resources-Archive hierarchy
If switching from an old app: always migrate Projects (active, day-to-day material). Migrate Areas only if AI indexing of those responsibilities adds value. Resources are optional. Archives should almost never be migrated — treat them as a sealed time capsule in the old system. Migrating archive material is the single biggest source of wasted time in tool switches.

// What does the RTO Method look like in real situations?

A freelance designer has used a simple to-do list and notes app for three years. They have just taken on a part-time team management role and their current stack cannot handle shared projects or client communication tracking.

This is a 3-to-5-year cycle transition triggered by a role change. Run Step 2: Must-Haves now include shared project views and client tagging; Can-Live-Without includes advanced calendar features. Step 3: the pain is concentrated in Tasks and possibly Notes — evaluate whether an all-in-one workspace like a collaborative task manager covers 80% of Must-Haves or whether a specialist project tool is needed. Step 5: migrate one active client project into the trial app for 90 days, journaling weekly. Do not migrate the full archive of past client notes.

A knowledge worker is overwhelmed by productivity content online and has switched apps four times in six months, each time spending days on migration and template-building before abandoning the new tool.

This is the JTO anti-pattern (Jump, Transfer, Obsess). Diagnose: no genuine phase transition has occurred — switching is driven by shiny-object syndrome. The fix is to return to Step 2 and write explicit Must-Haves vs. Can-Live-Withouts before looking at any new app. If the current app meets all Must-Haves, do not switch. If gaps exist, run a proper 90-day forced trial on one project only, not a full migration, and commit to the journal process before making any verdict.

A solopreneur wants to evaluate whether AI tools are genuinely saving them time or just adding noise to their stack.

Apply the Admin-Efficiency-Errands ladder (Step 8). List every AI feature currently in use. Map each to a layer: Does it auto-tag or auto-sort (Admin)? Does it allocate tasks intelligently using something like smart frames (Efficiency)? Does it execute background micro-actions like auto-drafting emails or pulling shopping data (Errands)? Any AI feature that cannot be mapped to one of these three layers is likely hype — remove it. Prioritise features already operating reliably at the Admin layer, as that is where AI is most mature today.

// What mistakes should you avoid when selecting productivity tools?

Shiny object syndrome — switching apps because a tool is new or popular, not because your genuine needs have changed. Run RTO only when triggered by a real life or work phase transition.
The JTO anti-pattern: Jump to the newest cool app, Transfer all data in a massive migration, then Obsess and make it your identity — before abandoning it weeks later with duplicated data everywhere.
Migrating everything during a trial. Always trial with one single project. A full migration before the trial is complete means discovering a deal-breaker after you have already paid the full switching cost.
Building an all-in-one workspace that becomes more to manage than to get work done. If you are maintaining the system more than using it, strip it back immediately.
Treating archive data as something that must be migrated. Archives are a sealed time capsule — leave them in the old system and only move Projects and, selectively, Areas.
Skipping the weekly trial journal. Without a written record of what worked and what did not, you have no data to refine your Must-Haves list for the next Research pass, forcing you to repeat RTO a third or fourth time.
Choosing an all-in-one workspace without checking which of the 15 features you will actually use. If you use 5 features and they meet your Must-Haves, the other 10 are irrelevant — do not let unused features count against a tool, or count in its favour.
Assuming AI scheduling of tasks is reliable today. The decision of which task to do next involves hundreds of subconscious factors (energy, emotion, environment, digestion) that AI cannot yet fully model. Treat AI task scheduling as an assist, not a replacement for judgment.
Evaluating apps without first establishing Must-Haves vs. Can-Live-Withouts. Research without criteria just produces a longer shortlist and more confusion.

// What are the key terms in the RTO Method?

RTO Method: Francesco's three-stage framework for selecting a productivity tool: Research (establish Must-Haves, build a shortlist of three), Trial (forced 90-day single-project trial with weekly journaling), Optimize (align the tool to your role and industry to maximise longevity).
JTO Anti-Pattern: The common dysfunctional alternative to RTO: Jump to the newest popular app without research, Transfer all data in a massive migration, then Obsess about it publicly — before abandoning it weeks later. Coined by Tiago Forte as a contrast to the RTO Method.
Must-Haves vs. Can-Live-Withouts: The two lists that must be written before any app research begins. Must-Haves are non-negotiable deal-breakers; Can-Live-Withouts are desirable but sacrificeable features. Analogous to the non-negotiables and compromises when searching for a house.
Starter Kit: The three foundational tool categories every productivity stack must cover: a task manager, a note-taking app, and a calendar. Derived from David Allen's Getting Things Done. Everything beyond these three is a bonus.
The 3-to-5-Year Cycle: The typical interval at which a person's life or work circumstances shift enough to warrant re-evaluating their productivity stack. AI is compressing this to roughly 2-3 years. Only a genuine cycle transition justifies running the RTO Method.
Admin, Efficiency, Errands (AI Value Ladder): Francesco's three-layer framework for evaluating real AI productivity value. Admin: automatic organisation tasks (tagging, sorting, scheduling). Efficiency: intelligent workload structuring and allocation. Errands: background micro-actions executed autonomously. Hype claims that cannot be mapped to one of these layers should be ignored.
Moving House Analogy: Francesco's analogy for the relative switching cost of different tool categories. Note-taking app = moving house (hardest). To-do list app = moving car (medium). Calendar app = switching phones (easiest). Use this to calibrate how much migration effort and caution a switch deserves.
Smart Frames: A scheduling concept (seen in tools like Morgan) where a user defines energy-based time blocks for their week (e.g., light work in the morning, deep work midday, lighter work in the afternoon) and the tool auto-populates tasks that match each frame's criteria. Relates to the broader principle of energy-aware productivity.
Forced 90-Day Trial: The Trial phase of RTO. The user commits to a fixed 90-day period with their top candidate app before making any judgment. 'Forced' means resisting the urge to abandon or switch mid-trial. The commitment test: if you are already hesitant before starting, go back to Research.
Shiny Object Syndrome: The tendency to jump between productivity apps in pursuit of a perfect solution, driven by novelty and online hype rather than genuine unmet needs. The RTO Method's Research phase and the Must-Haves list are the primary defences against it.
Mother-in-Law Solution: Francesco's term for beginner-friendly app recommendations — tools he would recommend to a non-tech-savvy person that are simple enough to start with but capable of expanding as needs grow. Example starter picks: Todoist for tasks, Evernote for notes, Google Calendar for scheduling.
Agentic Workflows: AI-powered background processes that execute sequences of micro-actions across connected apps on the user's behalf — the 'Errands' layer of the AI Value Ladder. Currently emerging; the near-future state of productivity software where human involvement shifts from doing tasks to making decisions and creative work.

// FREQUENTLY ASKED QUESTIONS

What is the RTO tool selection method?

The RTO Method is a three-stage framework for choosing productivity tools: Research (define your Must-Haves and shortlist exactly three candidates), Trial (run a forced 90-day test using one active project while journaling weekly), and Optimize (align the winning tool to your specific role and industry for maximum longevity). It's designed to stop endless app-switching by tying tool decisions to genuine life or work phase changes.

What is the JTO anti-pattern in productivity?

JTO stands for Jump, Transfer, Obsess — the dysfunctional opposite of the RTO Method. You Jump to the newest popular app without research, Transfer all your data in a massive migration, then Obsess about it publicly before abandoning it weeks later, leaving duplicated data everywhere. Coined by Tiago Forte, JTO describes shiny-object app-hopping driven by hype rather than genuine unmet needs.

How do I know when to switch productivity apps?

Switch only when you're in a genuine 3-to-5-year cycle transition — a role change, new family situation, or new project type in the last 6-12 months — not because an app went viral. If your current tool meets all your Must-Haves, don't switch. Boredom and online hype are not valid triggers; real, documented pain in your stack is.

How do I run a 90-day trial for a new productivity tool?

Migrate one single active project — not your whole stack — into the new tool and run it start to finish. Keep a weekly journal noting what worked, what didn't, and whether missing features appear on the roadmap. Before starting, confirm you're genuinely willing to commit 90 days; if you're already hesitant, your research isn't solid enough.

What tools do I need in a beginner productivity stack?

Every beginner stack needs exactly three core tools: a task manager, a note-taking app, and a calendar. Start with native platform defaults like Apple or Google before graduating to third-party apps. Two to three apps is the right starting ceiling — everything beyond these three is a bonus, not a requirement.

How does the RTO Method compare to just trying apps until one sticks?

Trying apps randomly is the JTO anti-pattern — it produces repeated full migrations, duplicated data, and abandoned tools. RTO front-loads clarity by defining Must-Haves before research, limits your shortlist to three, and tests with one project over 90 days instead of a full migration. This surfaces deal-breakers cheaply and means you rarely need to run the process more than twice.

When should I use the RTO Method versus sticking with my current stack?

Use RTO when you've hit a genuine life or work phase transition or feel real friction — shared projects your app can't handle, tasks that feel like pure admin, or a stack so complex you maintain it more than you use it. Stick with your current stack if it still meets every Must-Have; a working system beats a novel one.

What results can I expect from using the RTO Method?

You'll lock in a tool stack that fits your current life phase, avoid the time and stress of repeated migrations, and stop chasing shiny objects. Because the 90-day trial and weekly journal build an evidence base, you'll rarely need to re-select more than twice. The end state is a simple, role-aligned stack you can stay in until your next genuine phase transition.

How do I evaluate whether an AI productivity feature is real or hype?

Map it against the AI Value Ladder's three layers: Admin (auto-tagging, sorting, scheduling), Efficiency (intelligent task allocation and workload structuring), and Errands (background micro-actions executed on your behalf). If a feature can't be mapped to one of these three layers, it's likely hype — remove it. Prioritize Admin-layer features, since that's where AI is most reliable today.

Which productivity tools should I migrate when switching apps?

Always migrate Projects — your active, day-to-day material. Migrate Areas only if AI indexing of those responsibilities adds value. Resources are optional. Archives should almost never be migrated — treat them as a sealed time capsule in the old system. Migrating archive data is the single biggest source of wasted time in tool switches.

Why does switching a note-taking app feel harder than switching a calendar?

Because of switching cost. In the Moving House Analogy, switching a note-taking app is like moving house (hardest — expensive in time and stress), a to-do list app is like moving car (medium), and a calendar is like switching phones (easiest). Match your migration caution and effort to each category's true switching cost, and migrate as infrequently as possible.

// GET THIS SKILL — FREE