How to Run a Jewelry Design Sprint With a Remote Team

Remote jewelry design teams have a coordination problem that is different from other creative disciplines. The work is highly visual, highly iterative, and highly dependent on precise feedback. "Make it a bit more delicate" means something very specific — and something very different depending on who said it, what they were looking at when they said it, and whether anyone wrote it down.

In a physical studio, a lot of this gets resolved by proximity. You walk over, point at the piece, and show what you mean. Remote teams don't have that option, and the substitutes — long email threads, screenshot-heavy Slack messages, video calls that end without clear next steps — accumulate into coordination overhead that slows everything down.

Studio's Spaces and annotation system are built to run a structured design sprint remotely without any of that overhead.

Setting up the Sprint Space

A Space in Studio is a project management workboard for design work. Create one at the start of each sprint with a clear title — collection name, client name, and sprint number works well. Set a due date for the sprint end. Assign the Space owner.

Inside the Space, create tasks that map to each stage of the sprint. The structure depends on your process, but a typical jewelry design sprint breaks into recognizable phases: brief, concept generation, internal review, client review, revisions, final approval. Create a custom section for each phase so tasks can move through them as work progresses.

Each task gets a title, an assignee, a due date, and a priority. For a sprint, the due dates are not aspirational — they are the sprint schedule. Every team member can see the full board, see who owns what, and see what is blocking.

Brief to concept: the generation phase

The first tasks in the sprint are typically the generation tasks. A designer receives a task with the brief attached, generates concept designs in Studio, and links the resulting projects back to the task from the Links tab. The project link appears in the task's activity timeline automatically.

When the designer marks the task complete, the assignee gets a push notification. No status update message needed — the system handles the handoff.

If the brief requires multiple designers generating different parts of the collection, the Kanban board makes the parallel work visible. Cards in the Generation column show who is working on what and what is still pending, without anyone having to ask.

Internal review: annotations instead of meetings

The review phase is where most remote design teams lose time. Without a structured tool, review happens over email or Slack — screenshots attached, feedback written in prose, revisions applied without a clear record of what changed and why.

In Studio, the reviewer opens the design project, switches to Annotate mode, and draws directly on the image. They circle the element they're commenting on, write the specific feedback as a comment attached to that mark, and optionally assign it to the designer for action. The annotation is scoped to that specific image variation, so a project with ten variations has ten independent annotation threads rather than one tangled conversation.

Annotation deep links let reviewers share a specific annotation in a Slack message or email — the link navigates directly to the correct project, variation, and annotation. No more "third image, the comment about the prong style."

When an annotation is added, the project owner and image creator each receive a push notification. Replies create a thread under the original annotation. When the feedback is addressed, the annotation is marked resolved. At the end of the review cycle, the unresolved count tells you exactly what is still outstanding.

Client review: external access without account creation

Once internal review is complete, the approved concepts go into a Catalog and a named external share link goes to the client. The client opens the Catalog in their browser, annotates directly on the designs they want to comment on, and the feedback lands in the Activity Feed immediately.

The client does not need a Studio account. They do not need to download anything. They click the link and they're in. Their annotations appear alongside the internal team's in the same Activity Feed, timestamped and attached to the specific pixel they were pointing at.

The sprint task for client review can stay open until the client's feedback is received. When it lands, the task moves to the Revisions column and a new task is created for each piece that needs changes, assigned to the appropriate designer.

Revisions and final approval

Revision tasks link back to the original project and carry the specific annotation feedback as context. The designer works through the revisions in Studio, marks each annotation as resolved as they go, and updates the task status when the revision is complete.

The sprint lead can monitor the Kanban board throughout without messaging anyone for updates. Cards moving through columns, annotation counts dropping, tasks completing — the board tells the story of the sprint without status meetings or Slack threads.

When all revision tasks are complete and the final designs are approved, they go into the catalog for export. The sprint is done.

A few things that make this work better in practice

Recurring tasks are useful for sprint rituals that happen on a fixed schedule — daily async check-ins, weekly review syncs, sprint retrospectives. Set the recurrence once and the tasks advance their due dates automatically. If a task's due date passes without completion, the system advances it to the next scheduled date so it stays visible rather than silently going overdue.

The Consolidated Todos view shows every task across every Space assigned to the current user in one flat list. For a designer working across multiple sprints simultaneously, this is the daily task list — no need to open each Space individually.

@mentions in task comments trigger push notifications to the mentioned person. For anything that needs someone's attention right now rather than in the natural flow of their task queue, a mention is the direct line.

The AI Auto-Create from Transcript feature is worth using at the end of any planning call that does happen. Paste the transcript or meeting notes, let the AI extract the action items, assign them to the right people in one step, and the next sprint is structured before you close your laptop.