Structuring Your Workspace

How to decide what becomes a project, a department, or a process category.

Before you invite your team, decide how to organize the work. Getting this right up front keeps Architect's analysis sharp and gives you the views you want later. Linc has three levels:

  • Project — the top-level container, and the unit Architect analyzes. Everything inside a project is analyzed together.
  • Department — a team or function within a project (Accounting, IT, Operations). Organizes the hierarchy and how the analysis is grouped.
  • Process category — a specific workflow or group of related workflows within a department (Accounts Payable, Accounts Receivable, Month-End Close).

How to Decide

A project can hold many departments, and each department can hold many process categories. The only real decision is where to draw the project boundary. Use this rule of thumb:

  • Group into one project when the work shares systems and you would want to see its opportunities compared side by side.
  • Split into a separate project when it is a genuinely different domain that would dilute the analysis.

Architect runs across an entire project at once. If you mix unrelated domains (for example, IT helpdesk tickets next to month-end close), the analysis spreads thin and the output is less sharp for both. Keeping each project focused gives you stronger, more relevant opportunities.

Worked Example

A corporate finance and transformation effort would be set up like this:

  • Project: Corporate Transformation
  • Department: Accounting (add Operations, Investments, and other corporate teams as departments as they come online)
  • Process categories under Accounting: Accounts Payable, Accounts Receivable, Month-End Close
  • Separate project: IT (helpdesk, infrastructure, application support), kept apart because it is a different domain with different systems
Tip
Keep related processes (A/P, A/R, Month-End Close) as process categories under one department, not as separate projects. You will usually want to see how they connect (for example, how AP inquiries feed into month-end), and separate projects hide those links.

Seeing Across Projects

You do not need to merge everything into one project to get a cross-department picture. Use the project switcher and the All Projects view in the sidebar to move between and review work across projects. Org-wide analysis that runs across multiple projects in a single executive view is on the roadmap, so you can keep each project focused today and still get the corporate-wide rollup as it ships.

Interview Categories

Interview categories (the topics Scout tracks during a recording) follow the same hierarchy. You can define a consistent set at the organization level so every project inherits it, then add department-specific or project-specific categories where a team needs them. Set these up alongside your departments before sending invitations.

Avoid over-splitting
Do not create a separate project for every process. Giving A/P its own project, for instance, fragments the analysis and loses the connections between related workflows. Start with one project per domain, departments within it, and process categories within those.