Documentation source

Taylor the Guest Viewer

External consultant invited to view a workspace. No onboarding, no training, cautious by nature.

## Background

Taylor is a senior consultant at an external advisory firm hired to evaluate a subset of portfolio companies for a PE fund. They received an email invitation to a workspace with a short message: "Here is access to review the pipeline data we discussed." They have never seen this platform before, do not know its terminology, and have no onboarding session scheduled. Their entire mental model comes from the invitation email, whatever the login screen tells them, and whatever the UI reveals after they get in.

Taylor works across four different client engagements simultaneously, each with its own tools and portals. They have high general software literacy but zero product-specific knowledge. They are cautious by nature — as an outsider with limited permissions, they worry about accidentally triggering a notification to the internal team, changing a value they should not touch, or seeing data they were not meant to see. They will spend roughly 30 minutes in the platform per visit, usually on a laptop during back-to-back calls, and need to extract what they need quickly.

## Mindset & Behavior

- I read every label carefully on my first visit because I have no idea what the platform's vocabulary means. If a section is called "Entities" or "Records" without context, I will hesitate before clicking.
- I hover before I click. If a button or link does not have a tooltip or a visually distinct disabled state, I will avoid it rather than risk triggering something I cannot undo.
- I expect the interface to tell me what I can do, not just what exists. A list of items with no indication of my permissions is anxiety-inducing.
- I will test boundaries deliberately — I will try to click an edit button, try to delete something, try to access a page from the nav that might be restricted — to understand where my limits are. I need those limits to be communicated gracefully.
- I do not trust "empty" pages. If I see a blank list, I cannot tell whether there is no data, I lack permission to see it, or something failed to load. The difference matters.
- I will not sign up for a new account or install anything. If the login flow is confusing or requires steps beyond entering my credentials, I will email the person who invited me instead.
- I pay close attention to what the navigation shows me. If I can see menu items for features I cannot access, that feels like a broken experience. If the nav is trimmed to only what I can use, I feel oriented and safe.
- I take notes outside the platform (in my own docs) because I assume I cannot annotate or comment within a guest role. If comments are available to me, I need the UI to make that obvious.

## Background Taylor is a senior consultant at an external advisory firm hired to evaluate a subset of portfolio companies for a PE fund. They received an email invitation to a workspace with a short message: "Here is access to review the pipeline data we discussed." They have never seen this platform before, do not know its terminology, and have no onboarding session scheduled. Their entire mental model comes from the invitation email, whatever the login screen tells them, and whatever the UI reveals after they get in. Taylor works across four different client engagements simultaneously, each with its own tools and portals. They have high general software literacy but zero product-specific knowledge. They are cautious by nature — as an outsider with limited permissions, they worry about accidentally triggering a notification to the internal team, changing a value they should not touch, or seeing data they were not meant to see. They will spend roughly 30 minutes in the platform per visit, usually on a laptop during back-to-back calls, and need to extract what they need quickly. ## Mindset & Behavior - I read every label carefully on my first visit because I have no idea what the platform's vocabulary means. If a section is called "Entities" or "Records" without context, I will hesitate before clicking. - I hover before I click. If a button or link does not have a tooltip or a visually distinct disabled state, I will avoid it rather than risk triggering something I cannot undo. - I expect the interface to tell me what I can do, not just what exists. A list of items with no indication of my permissions is anxiety-inducing. - I will test boundaries deliberately — I will try to click an edit button, try to delete something, try to access a page from the nav that might be restricted — to understand where my limits are. I need those limits to be communicated gracefully. - I do not trust "empty" pages. If I see a blank list, I cannot tell whether there is no data, I lack permission to see it, or something failed to load. The difference matters. - I will not sign up for a new account or install anything. If the login flow is confusing or requires steps beyond entering my credentials, I will email the person who invited me instead. - I pay close attention to what the navigation shows me. If I can see menu items for features I cannot access, that feels like a broken experience. If the nav is trimmed to only what I can use, I feel oriented and safe. - I take notes outside the platform (in my own docs) because I assume I cannot annotate or comment within a guest role. If comments are available to me, I need the UI to make that obvious.