Explore bring your people into the possibility.
Some ideas need more than one kind of human judgment. Invite colleagues into a Supanova workspace, give them access suited to their responsibilities, and put a workforce of AI specialists behind the project they share. Your people contribute the context, make the decisions, and review what comes back.
Imagine a small team turning years of hard-won experience into a public workshop. The founder knows what the workshop should make possible. A subject expert knows where people usually get stuck. An operations teammate knows what participants need before they arrive. All three can see a useful result: a session people can follow, an exercise worth doing, and an invitation that tells the truth about what attendees will leave with.
The preparation has many parts. Someone must organize the source notes, find the thread that holds the lesson together, draft the exercise, and turn it into a clear invitation. Supanova gives the team a shared place to direct that connected work. A project can hold the brief and relevant sources while AI specialists help research, structure, write, and check the material.
Illustrative example: a workshop project prepared by a team.
Prepare a 90-minute workshop on making better project handoffs. Use our approved teaching notes for the method. Draft a session outline, one practical exercise, and a participant invitation. Flag claims or activities the notes do not support. Bring all three pieces back for review before we publish anything.
The project lead reviews the plan and makes sure the workshop has a clear promise. The subject expert reads the proposed exercise and spots a problem: it asks participants to diagnose an entire organization in ten minutes. They ask for a narrower activity built around one handoff. Operations notices that the invitation promises a completed process map, while the session can realistically help each person leave with a first draft.
Those comments change the work. The workforce can prepare a revised exercise and invitation from the team's direction. The people who own the promise decide when each piece is ready.
Illustrative excerpt from the revised invitation:
Bring one handoff that regularly loses context. You'll leave with a first draft of the questions, owners, and next steps that handoff needs. You can refine it with your team after the session.
The workshop is still the team's idea. The preparation has acquired a plan, a workforce, and a reviewable finish.
Members can enter the same workspace, bring relevant knowledge to projects, follow progress, and review work according to their roles and permissions. Someone can contribute source material or feedback; someone with the required authority can approve a plan or deliverable. The team chooses how to share those responsibilities.
As work moves, Activities can surface requests for input, approvals, and new deliverables. The project keeps its brief, tasks, and versions together. A teammate returning after another meeting can see what needs a decision and what is ready to inspect. That matters when a project depends on several people whose calendars rarely line up.
The same pattern could carry a product release, a community event, or a customer research program. Your team gives the workforce a shared destination; each person adds the judgment only they can supply. For work organized by business function, explore Multiple departments. For separate ventures or bodies of work, explore Multiple workspaces.
Do colleagues need to start separate workspaces?
No. Invite them into the workspace where the work belongs. Each person can have access appropriate to their role. If you are running a separate venture with different context and members, a second workspace may fit better.
Can everyone approve the work?
Approval depends on the member's permissions and the workspace's settings. Give review and approval responsibility to the people who can make those decisions for the project.
Can teammates change a result after it comes back?
People with the right access can give focused feedback, request revisions, and inspect the next version. The team can accept the result it is willing to use. Sending or publishing it is a separate action.
Start with a project your team already wants to pursue. Invite the people who know the audience, the work, and the promise. Give them a workforce to carry the preparation toward a result they can stand behind together.
Launch a new workspace
Previous: Multi-model · Next: Multiple departments · Back to Feature Catalog
Launch a new workspace