PRODUCT REVIEW / SEPTEMBER 25
From a visual workspace
to a working design studio.
A candid assessment of the current app—and the order that makes the next work useful.
THE VERDICT
The direction is working.
The collaboration needs a backbone.
Keep the visual-first shell, combined direction, collection and outfit views. Build review, asset history and access around them. Do not add more disconnected screens or expose anonymous editing to make the app look collaborative.
KEEP AND STRENGTHEN
- Imagery and creative work ahead of administration.
- Proposed direction clearly separated from approval.
- One consistent mobile/desktop workspace.
- Click-through relationships between looks, products and references.
- Public review browsing while shared writes remain protected.
CHANGE NOW
- Stop using one placeholder silhouette for unrelated products.
- Expose clear review status and the exact asset being discussed.
- Label personal-device features separately from shared team work.
- Replace static priority copy with real review and task state.
- Make access, empty states, errors and unfinished features explicit.
NEXT VERTICAL SLICE
Make review a real conversation.
Put feedback on the exact piece of work—not in a separate generic comment box.
- One review page per concept, board, outfit or uploaded asset.
- Pin comments to an image and distinguish a question, suggestion and change request.
- Reply, resolve, and reopen threads while retaining the original discussion.
- Give reviewers revocable team access without making the public site editable.
PASS / FAIL TEST
Two people open the same concept. One adds a pin; the other replies, reloads, and sees the same thread. The activity identifies the correct person. A public visitor cannot write.
Today: public viewing works; protected comments exist against a small set of brand artifacts. Product-level threads, annotation and invitation flow are not built.
FOUNDATION
Make the work traceable.
A decision is only useful if everyone knows which version it applies to.
- Upload source files to a managed library with thumbnails, contributor/source information and tags.
- Keep immutable versions instead of replacing an image in place.
- Compare versions side by side; approvals remain attached to the reviewed version.
- Connect each extracted moodboard fragment to the original file and crop coordinates.
PASS / FAIL TEST
Upload revision 2 of an asset. Revision 1 comments and approval remain visible on revision 1; revision 2 does not inherit approval. A removed reviewer cannot retrieve protected files.
Today: original references and crop provenance exist, but assets are deployed files. There is no upload interface or durable multi-version review workflow.
AFTER REVIEW + VERSIONS
Turn decisions into forward motion.
Connect accepted direction to design tasks, samples, reviews and calendar events.
- Create a change request from a comment without retyping its context.
- Track proposed, in review, changes requested, approved and archived states consistently.
- Show what changed since a teammate’s last visit, with links to the actual work.
- Show useful next actions based on missing evidence and dependencies—not invented AI certainty.
PASS / FAIL TEST
A resolved review request links to its task, revised asset and decision. The team can identify what is blocked and what changed without reconstructing chat history.
Today: basic server-backed tasks and calendar create/delete exist. Full editing, reliable dependency links, audit history and notifications are missing.
BEYOND APPAREL
Generalize the structure.
Keep each team’s world distinct.
A reusable design-team app needs projects, assets, concepts, boards, versions, reviews and decisions as its core objects. Apparel categories should be a project template—not hardcoded into the platform. Architecture, packaging, interiors and campaign teams can share the workflow without sharing their confidential content or being forced into a clothing catalogue.
Shared platform
Project isolation, access, asset library, versions, annotation, review states, activity, search and export.
Project-specific tools
Product/room/campaign categories, spec fields, vocabulary, brand palette, review checklist and milestone types.
Multi-project and multi-tenant isolation are not implemented. The current deployment is one Course Conditions workspace, not a safely separated service for unrelated client teams.
RELEASE STANDARD
Useful before elaborate.
Every feature should work for two real people, persist across reloads, identify what changed, prevent unauthorized edits, and remain usable on mobile and keyboard. Add recovery and consistent backups before inviting broader teams. Automated tests support these checks; they do not replace the team’s actual use and approval.
Back to the unified direction ↗