Project Management

Overview

Project Management helps you keep all boards, workflows, sessions, and result history in one place per project—so you can track work by client brief, course, or design phase.

Who it is for: Architecture and interior design students, freelancers, and small studios who need to manage AI experiments clearly by project.

When to use it: Use Project Management when you start a new brief, want to separate work by client or course, have many AI experiments and need to avoid mixing options, or want to return to an old project and immediately see its context.

Working structure in NamO Academy Studio

• **Project (Dự án):** Groups work by client brief, course, or design phase.
• **Board:** A workspace to gather input, references, AI outputs, and iterations for a specific goal.
• **Workflow:** The AI process you run inside a board (e.g. generate, edit, camera sync, refine).

Quick way to think about it: **Project** is the “work folder”, **Board** is the “work surface”, **Workflow** is “how you run an AI task”.

What It Solves

Key Capabilities

• Create, rename, and delete projects.
• Navigate boards by project.
• Create multiple boards within the same project (e.g. Concept, Materials, Lighting, Final Options).
• Organize workflows inside each board to track image creation, edits, and refinements.
• View quick project summary (cover image, board count, history, storage if available).
• Keep result history in project → board → workflow context for review and reuse.

How It Works (Workflow)

Step 1 /6

Go to the Projects screen and create a new project.

Step 2 /6

Name it by client brief, course, or concept direction.

Step 3 /6

Open the project.

Step 4 /6

Create boards by work goal (e.g. Concept, Materials, Camera Angles, Final Options).

Step 5 /6

Inside each board, run the right workflows (generate, edit, camera sync, refine) to create and iterate options.

Step 6 /6

Use board and workflow history to review, pick the best options, and refine or export.

Inputs

• Project name (required).
• Project description (optional, if available).
• Boards created in the project by work goal.
• Workflows run inside each board.
• AI-generated images from workflows (shown in project/board context).

Outputs

• A project list you can recognize quickly by name and cover image.
• Clear project → board → workflow structure.
• Result history per board/workflow for review and reuse.
• Full working context when returning to an old project.

Controls and Parameters

• Project name (required) — Used for navigation, search, and telling projects apart. Suggested patterns: Client_Space_Phase or Course_Assignment_Week.
• Project cover image (optional) — Aggregated from images created in the project's workflows, so it reflects current status and design direction at a glance.
• Board (within project) — Splits work within one project by a clear goal (concept, materials, lighting, camera, final options). Separate boards make review and comparison easier and keep results from different directions from mixing.
• Workflow (within board) — The AI process you run to create, edit, or refine images. Workflows keep input/reference context, prompts and attributes, and result history per run.

Using Boards (within a project)

A board is where you work visually with input images, references, prompts and attributes, AI outputs, and iterations. Each board should match one clear goal instead of mixing everything in a single board.

How to organize boards effectively

• **Concept** — explore initial options.
• **Materials** — try materials or styles.
• **Lighting** — compare lighting and mood.
• **Camera Angles** — try viewpoints and composition.
• **Final Options** — shortlist the best options for review.

When to create a new board?

• The goal of your experiments changes clearly (e.g. from concept to materials).
• You want a clear history per direction.
• The current board has too many results and is hard to review.

When to keep using the same board?

• You are still iterating on the same design direction.
• Only small changes (prompt, lighting, material).
• You want to compare variants in the same context.

Using Workflows (within a board)

A workflow is a specific AI process you run inside a board to create or refine images.

Examples:

• **Generate** (create new images).
• **Edit / Inpaint / Outpaint** (edit images).
• **Texture Transfer** (transfer style or material).
• **Refinement / Upscaling** (refine or increase resolution).

How to choose the right workflow

• Use **Generate** when you want new options from prompt / input / reference.
• Use **Edit / Inpaint / Outpaint** when you have a near-correct image and only need to change a region.
• Use **Texture Transfer** when you want to keep the subject but try material or style from a reference.
• Use **Refinement / Upscaling** when you have a good option and want to improve quality or resolution.

Using workflows in a project effectively

• Keep workflows aligned with the board goal (e.g. a “Materials” board focuses on generate / texture / refine for materials).
• Use consistent prompts and attributes to make comparison easier.
• Use workflow history to review changes across iterations.
• Move good results to a suitable board (e.g. from “Concept” to “Final Options”) if your process needs it.

Tips for organizing Project–Board–Workflow

• 1 project = 1 real brief (client / assignment / exercise).
• 1 board = 1 clear goal (concept / materials / lighting / camera / final).
• 1 workflow = 1 type of AI task (generate / edit / camera sync / refine).
• Avoid putting all experiments in one board if you want easy review.
• Use a “Final Options” board to gather the best images from other boards before export.

Common Use Cases

• Students: One project per assignment; boards like Concept, Materials, Final Options; generate + refine workflows for pin-ups.
• Freelancers: One project per client; one board per concept direction; edit/inpaint workflows to adjust shortlisted images quickly.
• Small studios: Boards by discipline (exterior, interior, materials, lighting); workflows let the team review by round.
• R&D / experimentation: A “sandbox” project; boards by model or prompt strategy to compare and reuse the best results.

Limitations and Known Behaviors

• Project Management in NamO Academy Studio is designed to organize AI visualization workflows—it does not replace full task management software.
• The project cover aggregates AI-generated images from workflows in the project (you cannot upload a separate cover-only asset).
• Project metadata detail may vary by product version or configuration.

Best Practices

• Create one project per real brief instead of lumping everything together.
• Name projects clearly from the start so you can find them again weeks later.
• The project cover is aggregated from images created in the project's workflows, so the Projects view reflects progress at a glance.
• Split boards by clear purpose (e.g. Concept, Materials, Camera Angles, Final Options).
• Archive old projects so your active list stays focused.

Audit Evidence

Project Management is a core organizational layer in NamO Academy Studio, not a standalone tool. Users create and run workflows in project and board context; inputs, prompts, and results are kept in that context to support history, reuse, and navigation across design iterations.

Operational Notes

At a high level, project management operations use the same platform infrastructure as other NamO Academy Studio workflows. Data is tied to the user and project context; some operations may be affected by system configuration, queues, or usage limits.

Related Features

• Boards
• Workflows