Roam Research Docs · Help & user documentation
roam/templates
- Dev docs #.h
- Tutorials::
- How-to guides::
- Reference
- Examples
- Community
- Roam Daily Template
- Designer:: Jonathan Borichevskiy
- Special Features::
- #Slider | #Tags | #TODO/DONE
- Templates::
- Last updated:: February 27th, 2021
- Weekly Agenda (created on a different day, and embedded with /Block Reference)
- Morning Questions
- {{slider}} How many hours of sleep did I get?
- What's one thing top of mind today?
- What's the one thing I need to get done today to make progress?
- Review #Index: Questions #values
- Agenda
- {{TODO}} Morning walk #goal-health #habit
- {{TODO}} Check calendar for scheduled events
- {{TODO}} Morning focus hour
- {{TODO}} Read 30 minutes #goal-learning #habit
- {{TODO}} Review Readwise.io
- {{TODO}} 10 minutes meditation #goal-health #habit
- {{TODO}} Workout or run #goal-health #habit
- {{TODO}} Evening focus hour
- {{TODO}} Do 7 - 30 - 90 review
- {{TODO}} read for pleasure, watch something, go for a walk
- Evening Questions
- List three things I'm grateful for #habit #gratitude
- What made me happy today?
- What made me sad?
- Where there any signs of my day going to shit that I could recognize?
- What prevented me from reaching my goals today?
- What am I looking forward to?
- Skeletons/Methods/Tags/Tools
- Designer:: Samuel Orion
- Special Features::
- Templates::
- Last updated:: July 1st, 2020
- Article::
- Topic:
- Tags:
- URL:
- Quotes / Summary:
- Comments / Questions:
- Book::
- Quotes / Summary:
- Comments / Questions:
- Topic:
- Tags:
- URL:
- Podcast
- Show:
- Speaker(s):
- Topic:
- Tags:
- URL:
- Summary:
- Videos
- Speaker:
- Tags:
- Summary:
- Link or Embed:
- Projects
- Due Date:
- Completed Date:
- Status:
- Related Goals:
- Success Criteria:
- Tags:
- Quarterly Preview
- Review Yearly Planning
- My biggest wins
- Process on annual goals for this quarter (% successful)
- Overall, what worked and what didn’t?
- What will you keep doing?
- What will you start doing?
- What will you improve?
- What will you stop doing?
- tools
- Find and replace
- KANBAN BOX
- {{kanban}}
- indent once for column title
- and another item
- this could be a great way to write an articles / thesis - very easy to read
- clock on the block to open the side bar - and see furtherinfo
- I was in column 2, now I am in column 1
- This is a second collum
- I was in column 1, now I am in column 2 - just click and drag
- indent again for items to put in list (ps look at the next level)
- A third column
- Daily Log
- Designer:: Mark Robertson
- Special Features::
- Code::
- Last updated:: July 1st, 2020
- #Morning Review
- #Weather Report
- Location:: #Home
- Weather Summary:: Weather Data (Summary)
- Conditions:: Weather Data (Condition) with Weather Data (Precipitation Chance)
- H/L Temp:: High - Weather Data (High), Low - Weather Data (Low)
- #Sleep Log
- Sleep Time::
- Sleep Quality::
- #Morning Pages
- #Morning Reflection
- {{query: {and: -1 Day Evening Pages {not: query}}}}
- Who benefits from your work?
- What am I grateful for?
- What do I want the day’s highlight to be?
- Daily Affirmations
- What am I think of?
- #Open Questions
- {{query: {and: Question TODO {not: {or:query DONE Templates}}}}}
- #Calendar
- #Family
- #Professional
- #Pedagogical Reflections
- #Daily Notes
- #Action List
- {{TODO}} Process Linked and Unlinked Mentions
- {{query: {and: TODO Action {not: {or: query Subtask:}}}}}
#Upcoming
- {{query: {and: TODO Scheduled {not: {or: query Action}} {between: Today's Date +2 Weeks}}}}
- #Evening Review
- {{TODO}} #Evening Pages
- Amazing things that happened
- What I have learned
- What could I have done better?
- #Capture Inbox
- The Roam Team
- Contact
- Name::
- Email::
- Company::
- Phone::
- Choice
- {{TODO}} Choice
- Context::
- Options::
- Decision::
- Daily agenda Updated
- Daily agenda
- {{kanban}}
- All day
- 00:00
- 01:00
- 02:00
- 03:00
- 04:00
- 05:00
- 06:00
- 07:00
- 08:00
- 09:00
- 10:00
- 11:00
- 12:00
- 13:00
- 14:00
- 15:00
- 16:00
- 17:00
- 18:00
- 19:00
- 20:00
- 21:00
- 22:00
- 23:00
- Need to plan
- An Engineering Problem Solving Process
- An engineered, systematic approach to problem solving can be invaluable in solving problems, capturing knowledge, and discovering solutions. An approach that I suggest involves starting with a simple outline consisting of the following sections (as appropriate - sometimes it makes sense to combine or eliminate certain sections). Feel free to delete this paragraph as you fill out the template.
- Problem Statement:: This should be a simple 1-2 sentence (no more!) statement of the problem. Do not describe symptoms. To the best of your ability, reduce the problem to its bare essence here. Over time this statement may be refined. A key principle is that if you cannot state your problem concisely, you probably don't know what it is and you almost certainly cannot communicate it effectively to others.
- Description:: Here you provide a detailed description of the problem.
- Describe why you want to solve this problem (if you do) and what, if anything, makes this problem particularly hard. This can be particularly valuable if you are considering writing new code. Sometimes after further evaluation you will realize it is better to use an alternative or take no action at present.
- Sometimes it is worth capturing the ideas but saving the solution for another time.
- Given:: List all things that have been provided to you, including facts, stories, etc.
- Required:: State all of the requirements to be met to provide a solution to the problem.
- Functional/User (Required): These are the things that a user must be able to do to solve the problem. They may be stated as user stories such as "As a user, I can do X so that Y." If you do not state who can do what and why, then the requirement is suspect.
- Nonfunctional/Technical: Technical requirements often revolve around criteria such as scaling, cost, operations, etc. I often recommend a different page for technical requirements as it is easy for problem solvers (especially developers) to move towards a technical solution (a form) prior to actually understanding the problem to be solved (the function).[1](((https://en.wikipedia.org/wiki/Form_follows_function)))
- Knowns:: State all the things you know about the problem. Provide links, references, citations, etc. as needed to trace the lineage of each known item.
- Unknowns:: What don't you know about the problem. Here you will try to anticipate the questions that you need to answer to better understand the problem.
- Alternative presentations of knowns and unknowns could include a Johari Window[2](((https://en.wikipedia.org/wiki/Johari_window))) or a "Rumsfeld-esque"[3](((https://en.wikipedia.org/wiki/There_are_known_knowns))) categorization.
- {{table}}
-
- Known to Others
- Not Known to Others
- Assumptions:: What do you believe to be true regarding this problem?
- Alternatives:: What alternatives already exist to this problem? What do you do now to solve the problem? What happens if you do nothing? If this is a technical solution, can an existing solution be used?
- Solution:: Based on all of the previous information, provide the solution to the problem. This could be a technical solution, process, new product, etc. Note that if multiple solutions are provided (suppose you provide multiple product offerings to solve the same problem) it is perfectly appropriate to have subpages for each solution.
- Recommendations:: An alternative to (or something to be used in conjunction with) a solution is one or more recommendations. Again, if appropriate recommendations can merit their own subpages.
- Hickey Design Process
- Problems
- Take wants/needs and translate them into problems
- Symptoms
- Requirements
- Knowns
- Unknowns
- What I don't know how to do
- Domain-side
- Solution-side
- Technical constraints (it has to compile to JS, for example)
- Unstated
- Things that everyone wants the system to avoid
- Doesn't crash, use too much memory, require too much energy, are examples of unstated requirements
- Solutions
- Solution A
- Benefits::
- Tradeoffs::
- Costs::
- Problem fit::
- Solution B
- Benefits::
- Tradeoffs::
- Costs::
- Problem fit::
- Course
- [Course name](course link) by
[[Author Name]] price
- 2-3 sentence blurb describing the course
- Theme
theme name
- Screenshots::
- Last updated::
- Designer:: name
- Twitter:: [link to bio]()
- Love this theme? Say thanks via [PayPal]() (and/or other payment service)
- Special Features::
- Code::
- Plugin
plugin_name
- Info::
- Must include GIF and/or video of usage
- Link::
- Getting started::
- Installation, activation and configuration
- Tutorials::
- Reference::
- Developer::
- Twitter::
- Love this plugin? Say thanks via [Paypal]()
- Code::
- Browser Extension
browser_extension_name
- Info::
- Must include GIF and/or video of usage
- Link::
- Getting started::
- Installation, activation and configuration
- Tutorials::
- Reference::
- Developer::
- Twitter::
- Love this plugin? Say thanks via [Paypal]()
- Coaching
Course Author Name
- Info::
- Website::
- Areas of specialty::
- Contact::
- Price::
- Docs #.h
- {{TODO}} Introduction (few bullets) and some GIFs
- Roam Team Videos::
- Articles::
- Community Videos::
- Key Commands::
- Video/article #.h
- {{TODO}} [Article link]() or {{video: }}
markdown version · view in Roam Research · exported 2026-07-03
