01 / Twelve weeks Open the weekly briefs

Twelve weeks, twelve briefs, one portfolio

Each week hands you a written brief, a five-point rubric and a deliverable you keep. Two live Figma labs run beside the briefs: one tool walkthrough, one critique round, both on Kyiv time and remote across Ukraine.

  1. W01Pitch the problemResearch frame and a one-screen problem statement.
  2. W02Screen inventoryAudit two Ukrainian services and map their flows.
  3. W03WireframesLow-fidelity frames for three core tasks.
  4. W04Type and spacingBuild a base scale and an 8px spacing ladder.
  5. W05ComponentsButtons, inputs, states and empty cases.
  6. W06Auto layoutOne component set with variants and properties.
  7. W07Responsive layoutFrom four columns on mobile to twelve on desktop.
  8. W08Accessibility basicsContrast, focus order and readable labels.
  9. W09PrototypingA clickable path from landing screen to result.
  10. W10Case study draftProblem, process and the decisions you made.
  11. W11Portfolio pagePublish the case study as a finished page.
  12. W12Final critiqueRubric scoring, handoff notes and next steps.
Section 03

Twelve weekly briefs, each with a rubric and a shipped artifact

See the rubric criteria

From an empty frame to a finished case study

Each week opens with a written brief and a live Figma lab. You hand in one artifact on Sunday, then carry it forward into the portfolio. Weeks six to twelve repeat the same rhythm at higher fidelity.

  1. Week 01Research

    Problem framing brief

    Interview two users, map the friction, and write a one-page problem statement with a measurable success criterion.

    Ships: research summary and problem statement

  2. Week 02Figma lab

    Wireframe to grid

    Rebuild a real Ukrainian service page on a 12-column grid. Frames, spacing scale, and a first pass at hierarchy.

    Ships: three wireframe frames plus a spacing sheet

  3. Week 03Components

    Component and variant set

    Turn the wireframe into a component library: buttons, inputs, cards, and the states each one needs in auto layout.

    Ships: component page with hover, focus, and disabled states

  4. Week 04Accessibility

    Contrast and keyboard pass

    Audit your own screens for contrast, focus order, and readable labels, then document every fix you made.

    Ships: annotated audit sheet

  5. Week 05Storytelling

    Case-study page

    Write the case study around the artifacts you already built: context, decisions, trade-offs, and the final screen set.

    Ships: published case-study page for your portfolio

04 / Rubric

Five criteria, published before week one

See the weekly briefs

How every assignment is scored

Each brief is graded against the same five criteria. Mentors write their notes beside your artifact, so you can see exactly which criterion moved your score.

  1. 01

    Research

    Problem statement, user evidence, and a written scope decision. Every claim carries a source or a stated assumption.

    20%
  2. 02

    Layout

    Grid logic, type scale, and spacing rhythm. Screens are judged at 1440px and 390px wide, not at a single hero shot.

    25%
  3. 03

    Components

    Frames, auto layout, and variants. A component has to survive a real content change without breaking its alignment.

    20%
  4. 04

    Accessibility basics

    Contrast passes, focus states are visible, and every form field has a label. Interactive states are documented, not implied.

    15%
  5. 05

    Story

    The case study explains the constraint, the decision, and the outcome in plain language. Screens alone do not count as a story.

    20%

06FAQ

Answers before you commit

Ask a coordinator
How much time does one week take?

Plan for about eight hours: two live Figma labs of 90 minutes each, plus one assignment brief with a written rubric. Learners who join the critique session spend a little longer and leave with mentor comments the same week.

Which tools does the curriculum require?

Figma is the main tool. Tool labs cover frames, auto layout, components, variants, prototyping and handoff. You also need a browser, a notebook for research notes and a way to export PDFs for your case studies. No paid plugins are required.

What does the certificate confirm?

You receive a certificate of completion from smarthomezk.com at the end of the 12 weeks. It confirms attendance and completed assignments. It is not a state-recognised diploma or a degree, and it does not guarantee a job, a salary or freelance income.

How many seats are in a cohort?

24 seats per cohort, remote from anywhere in Ukraine. Instruction runs in Ukrainian or English depending on the cohort, and live labs are scheduled in Kyiv time so working learners can attend after hours.

How are weekly assignments scored?

Five rubric criteria: research, layout, components, accessibility basics and case-study storytelling. Every brief is scored from 1 to 4 with a written mentor note, and you can revise once within the same week.

What are the next steps?

Read the weekly briefs to see the assignment chain, then write to a coordinator to hold a seat in the 2 June 2026 cohort.