Opportunity report

OneNote users forced into fragile nested-table hacks

OneNote users find default styles and table editing frustrating, so some adopt nested tables to represent hierarchical note levels. That workaround helps organization but raises maintenance, mobile usability, and portability concerns. Users (many with long-term OneNote usage) want improved table editing behavior and better mobile/interop support.

Worth it score 80High confidence5 signals12 evidence
Persona
1 evidence
Experienced OneNote users / power-users (some with a decade+ of use) looking for better ways to structure notes.

Right, I've been using OneNote for over a decade and never thought about this lol

view evidence on reddit
Pain
3 evidence
OneNote's default styles (font/color) and poor table editing make it hard to structure hierarchical notes; users feel forced to adopt nested tables and still worry about maintenance, mobile use, and portability.

Because the default styles have a font and color problem, I’ve come up with this organization method where the level of notes are represented by level of nested tables

view evidence on reddit

Kind of ironic, this *useful* application of nested tables, as table editing in 1Note is just shit. When cutting pasting content around, I always end up with unwanted nested tables. Table editing sucks IMO

view evidence on reddit
+1 more evidence

Won't it be too much effort to make them nested and maintain them when tables becomes large and heavy ?

view evidence on reddit
Workaround
3 evidence
Users create nested tables inside OneNote to represent hierarchical note levels (and add colors), treating tables as an organizational structure.

I've come up with this organization method where the level of notes are represented by level of nested tables

view evidence on reddit

I've used tables to keep things organized, but never thought of using nested tables. Glad you posted this!

view evidence on reddit
+1 more evidence

You can add table colors for better appearance/organization as well.

view evidence on reddit
Resistance
3 evidence
Nested-table approach can be heavy to maintain at scale; poor mobile/table editing and portability to other processors discourage adoption or make migration costly.

Won't it be too much effort to make them nested and maintain them when tables becomes large and heavy ?

view evidence on reddit

How well does this work on mobile devices?

view evidence on reddit
+1 more evidence

I imagine that would be a hell to copy that to a different text processor

view evidence on reddit
Desire
2 evidence
Users want better table editing behavior (move/copy rows/cells without creating unwanted nested tables), reliable mobile/tablet support, and easier portability between processors.

Table editing sucks IMO, the default behaviour should be to move or copy rows, cells, columns, not to introduced neste...

view evidence on reddit

How well does this work on mobile devices?

view evidence on reddit
Built by Signal Hunt · Every claim includes traceable evidence.