Frequently Asked Questions About Forte & Francesco RTO Tool Selection Method
22 answers covering everything from basics to advanced usage.
// Basics
What does RTO stand for in productivity tool selection?
RTO stands for Research, Trial, Optimize. Research means defining your Must-Haves and building a shortlist of exactly three candidate apps. Trial means running a forced 90-day test on your top candidate using one active project while journaling weekly. Optimize means aligning the winning tool to your specific role and industry to maximize how long you stay in it.
What is the 3-to-5-year cycle in productivity tools?
It's the typical interval at which your life or work circumstances shift enough to warrant re-evaluating your stack — a new role, family change, or project type. AI is compressing this to roughly 2-3 years. Only a genuine cycle transition justifies running the RTO Method; boredom or a viral app does not.
What is the Mother-in-Law Solution in tool selection?
It's Francesco's term for beginner-friendly app recommendations — tools simple enough for a non-tech-savvy person to start with but capable of growing as needs expand. Example starter picks include Todoist for tasks, Evernote for notes, and Google Calendar for scheduling. It's the practical entry point into a starter stack.
What is the Starter Kit and why only three tools?
The Starter Kit is the three foundational categories every stack must cover: a task manager, a note-taking app, and a calendar, derived from David Allen's Getting Things Done. Three tools is the right ceiling because it covers all essential workflows without creating a system that's more to manage than to use. Everything beyond these three is a bonus.
// How To
How do I write my Must-Haves and Can-Live-Withouts lists?
Write both lists before looking at any app. Must-Haves are deal-breakers whose absence ends a trial — be specific, like 'offline access,' 'recurring task support,' or 'calendar two-way sync.' Can-Live-Withouts are features you'd like but will sacrifice for simplicity or integration. Vague requirements produce bad selections, so precision here determines everything downstream.
How do I decide between an all-in-one workspace and specialist apps?
Check where your Must-Haves concentrate. All-in-one workspaces typically deliver an 80% experience across many functions, so if your non-negotiables are spread evenly, an all-in-one may work. But if your Must-Haves cluster in one category — like calendar hyper-features — keep that as a standalone specialist and compromise elsewhere. Never judge a tool on features you won't use.
How do I keep a useful trial journal during the 90 days?
Each week, note three things: what worked well, what didn't work, and whether missing features appear on the app's roadmap. This journal becomes your evidence base. At day 90 you either continue because the app passed, or you leave with a documented list of refined Must-Haves for your next Research pass — which is what stops you repeating RTO three or four times.
How do I optimize a tool once I've committed to it?
Find how people in your exact role or industry use the tool and learn every feature relevant to your Must-Haves. Treat optimization like moving into a house and making it yours — not continuous tinkering. The goal is longevity: resist re-opening the tool-selection question until your next genuine life or work phase transition.
// Troubleshooting
My new tool is missing a feature — should I abandon the trial?
Not immediately. Check whether the feature is a true Must-Have or just a Can-Live-Without, and look at the company's roadmap to see if it's incoming. If it's a genuine deal-breaker with no roadmap plan, document it and move to your ranked number-two candidate. If it's a nice-to-have, log it in your journal and keep going.
I keep switching apps every few months — how do I stop?
You're likely in the JTO anti-pattern driven by shiny-object syndrome, not a real phase transition. The fix is to write explicit Must-Haves and Can-Live-Withouts before touching any new app. If your current app meets all Must-Haves, don't switch. If gaps exist, run one proper 90-day single-project trial and commit to the journal before any verdict.
I already migrated everything before finishing the trial — now what?
This is a classic pitfall — a full migration before the trial completes means you may discover a deal-breaker after paying the full switching cost. Stop adding data, treat only your active Projects as live in the new tool, and leave archives sealed in the old system. Complete the 90-day journal on one project before deciding whether to fully commit or roll back.
My productivity system feels like more work than it saves — what's wrong?
It has failed the 'Keep It Dumb and Simple' principle: complexity is not sophistication. If you're maintaining the system more than using it to produce real work, strip it back immediately. Audit your all-in-one for features you actually use — if five meet your Must-Haves, the other ten are irrelevant and shouldn't justify a complex setup.
// Comparisons
How does the RTO Method compare to Getting Things Done (GTD)?
GTD is a task-management methodology for capturing and organizing work; RTO is specifically about selecting the tools you run any methodology in. RTO actually borrows GTD's insight that you need three core categories — tasks, notes, calendar — but adds the Research-Trial-Optimize process for choosing between apps. They're complementary: GTD tells you what to do, RTO tells you where to do it.
How is RTO different from just reading app review roundups?
Review roundups rank apps generically for an average user; RTO ranks them against your specific Must-Haves and life phase. Roundups also stop at recommendation, whereas RTO forces a 90-day single-project trial and a role-specific optimization stage. Reviews inform your Research shortlist, but they can't replace testing a tool against your actual workflow.
Is AI task scheduling better than deciding manually?
Not yet as a replacement. Deciding which task to do next involves hundreds of subconscious factors — energy, emotion, environment, even digestion — that AI cannot fully model today. Treat AI scheduling like Smart Frames as an assist that populates energy-based time blocks, not as a substitute for your judgment. It's most reliable at the Admin layer, less so at true Efficiency.
How does an all-in-one workspace compare to a best-in-class specialist app?
All-in-one workspaces deliver roughly 80% quality across many functions with the benefit of integration and fewer apps to manage. Best-in-class specialists deliver 100% in one category but require juggling multiple tools. The deciding factor is your Must-Haves: if the critical 20% you can't compromise on lives in one category, choose the specialist there and let an all-in-one handle the rest.
// Advanced
What are the three layers of the AI Value Ladder?
The AI Value Ladder has three ascending layers. Admin: automatic organization like tagging, sorting, and scheduling. Efficiency: intelligent workload structuring and task allocation, such as Smart Frames. Errands: background micro-actions executed autonomously on your behalf, like auto-drafting emails or pulling shopping data. Evaluate any AI claim against which layer it truly operates in, and ignore anything that maps to none.
What are agentic workflows and how do they fit the RTO Method?
Agentic workflows are AI-powered background processes that execute sequences of micro-actions across connected apps on your behalf — the 'Errands' layer of the AI Value Ladder. They're emerging now and point toward a near-future where human effort shifts from doing tasks to decision-making and creativity. In RTO, you'd audit them in Step 8, prioritizing only agentic features that reliably operate today.
How does the Admin-to-Decision-Making split reshape stack design?
Roughly 40% of a knowledge worker's day is administrative clerical work, and AI is absorbing that layer. What remains is the quality of your decision-making and creativity. So design your stack around serving those two outputs, not around managing overload. Tools that merely help you shuffle admin are becoming less valuable than tools that sharpen judgment and creative output.
How deep should my research go before starting a trial?
Deep enough to confidently rank three candidates 1, 2, 3. Number one is your primary trial candidate; two and three are fallbacks. Use independent reviewers, category-specific comparison sites, and community feedback — not just the app's own marketing — and check company roadmaps for incoming features. The test: if you're hesitant to commit 90 days, your research isn't finished.
How does the Moving House Analogy change my migration strategy?
It tells you to match caution to switching cost. A note-taking app is 'moving house' — the hardest, so migrate rarely and carefully. A to-do list is 'moving car' — medium effort. A calendar is 'switching phones' — easiest. Combine this with the Projects-Areas-Resources-Archive hierarchy: even for a hard note-app switch, migrate active Projects, selectively Areas, and leave Archives sealed.
How often should I realistically run the RTO Method?
Ideally once per genuine life or work phase transition — roughly every 3-5 years, or 2-3 with AI compressing cycles. If you research thoroughly and journal your trial, you'll rarely run it more than twice in a single transition. Running it more often than that is usually a sign of shiny-object syndrome rather than real unmet needs.