Organize product and team work with Glass

Overview

Early Access. For access information, see Request access to Glass.

Use a shared Glass project to prepare and update a cross-functional team plan from the team's approved context. Bring together goals, milestones, confirmed owners, dependencies, and open questions without filling gaps with invented dates, assignments, or approvals.

Who this is for: Product leads and cross-functional teams coordinating a project or initiative.

Prepare your Glass planning sources

Gather the following approved context before setting up the workflow. Use reference examples for structure and style, not as proof of current facts or approval to take an action.

• Approved planning rules and a source hierarchy.
• A product or project brief with goals, scope, success measures, and constraints.
• A dated decision log and a team roster with confirmed responsibilities.
• Current milestones, dependencies, risks, and open questions.
• One team-plan example for structure and style only.

Review who can access your project before adding sensitive information. If you need information from a connected app, check the project's plugin access; a personal connection is not proof that the project can use it.

Set up your Glass team-planning workflow

For Slack, first check app setup and access. After installation and Glass authorization, invite Glass to the intended internal channel and mention @Glass. Use its channel-linked project, not a separate new project. Otherwise, use a shared project in Glass.

Check the audience and connected accounts before adding the sources listed above. Paste this prompt and review the proposed guidance.

Draft reusable team-planning guidance using the sources I provide:

- Follow the approved source hierarchy and later explicit decisions that supersede older baselines. Use reference plans for style only.
- Use the roster only for confirmed owners; never invent, infer, recommend, rank, or choose owners. Leave unconfirmed assignments unresolved.
- Ask a focused question about missing information or conflicting controlling sources.
- Produce a concise plan with status, goals, measures, scope, milestones, workstreams, confirmed owners, dependencies, risks, decisions, open questions, collaboration cadence, and immediate actions.
- Label outputs Draft for team review. Return them to this project or linked Slack channel.
- Retain standing feedback only with explicit team approval. Keep one-off changes and project-specific decisions in the current plan or decision log.

Never invent facts, owners, dates, budget, approvals, launch commitments, or capabilities. Do not approve spend, change permissions, publish externally, or create tasks in another system without explicit confirmation.

Identify missing sources or connections and show the guidance for approval before applying it.

After checking source rules, audience, and review requirements, approve the guidance and follow Save and reuse instructions in a Glass space.

Prompt instructions do not restrict a connected account's permissions; review Glass access to connected apps separately.

Create or update a team plan in Glass

Name the project, planning stage, review milestone, and changes since the previous plan. Ask Glass to apply the approved source hierarchy and return an editable draft with a short summary of changes, blockers, items needing confirmation, and next actions.

Create or update the cross-functional team plan using this project's approved sources. Read the saved workflow and source-rule files: [File names].

Project: [Project or initiative]
Planning stage: [Stage]
Requested review milestone: [Milestone]
Known changes since the last plan: [Changes]
Output: Editable team plan for review

Follow the source hierarchy, apply the latest explicit decisions, and use reference examples for structure and style only. Keep the output labeled Draft for team review. Make unresolved owners, approvals, dependencies, and conflicts visible instead of inventing them.

Return the draft to this shared project or linked Slack channel with a short summary of what changed, what is blocked, what needs confirmation, and the next three actions.

Missing owners, spend approval, and external launch commitments must stay unresolved until an authorized person confirms them. Do not approve spending, publish externally, or create tasks in another system as part of an unreviewed plan.

For a Slack-based request, first check how to message Glass and link the intended channel. Check the project audience before using a channel. The Slack app and a personal Slack plugin connection are separate; do not assume connecting your personal account installs the app.

Review the Glass plan with your team

Keep the result as a draft until you have checked it against the approved sources. Ask Glass to make gaps and conflicts explicit instead of filling them in, and review any requested follow-up before it changes records or reaches another audience.

• Compare the plan with the current decision log. A later explicit decision can supersede an older milestone baseline; a suggestion is not an approved date change.
• Check goals, scope, milestones, dependencies, risks, and next actions against their sources. Confirm that requested owners were actually assigned by the team.
• Do not let Glass choose or recommend an owner from the roster. Leave unresolved assignments as "Unassigned - confirmation required" until the product lead confirms them.
• When you confirm a project-specific decision, ask Glass to update that project's plan or decision log without silently changing the reusable workflow. Approve standing guidance changes separately.

All starter workflows