Wide Research | Broad research
Represent broad research as one question distributed across many tasks and returned to one result table. Emphasize expansion and aggregation rather than crowding the screen with windows.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Wide Research|Broad research · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Open the workspace from one task
Begin with only the research input and scope, then reveal subtask panels after submission. Spread them in depth and a grid while keeping the main task easy to locate.
Light backgrounds, fine borders, and soft shadows support dense information; accents identify current work, and headings, names, and fields share a sans-serif font.
Make parallel task counts readable
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Wide Research|Broad research · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="11" data-end="28"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Introduce subtasks in batches and label running and completed states separately. Shrink windows as numbers grow, but keep titles recognizable; use the counter to communicate scale and windows to communicate division of work.
Turn completed subtasks into uniform records and gather them into the table one by one. Converge toward the result center rather than sending windows randomly out of frame.
The result table needs consistent fields
Choose columns such as subject, organization, or research focus that support the conclusion. Keep headers fixed and fill rows gradually; export is the final action after the result.
For user research, competitors, or design resources, first define the question each subject must answer, then arrange subtasks and the table. Preserve the one-to-many, then many-to-one working relationship.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to batch design reviews or competitor research, preserving decomposition→parallel work→summary
- Subject counts may change, but totals must remain consistent
Production constraints
Task input / Parallel subtasks / Completion count / Summary table / Deliverable file
- Split one input into multiple task panels, unfolding them horizontally in depth to express parallel execution
- gather subtask results into one table, with quantity changes tied to task completion
- end with a downloadable file rather than only a completion state