AACE AI SW
👤ParticipantACE AI SW
DAY 07 · TUESDAY · PLAN & REVIEW · PROJECT WEEK

AI-driven project design &
mid-term presentation

Based on the problem and scope agreed on Day 6, design one core user flow down to screens, data and API. The morning focuses on team design; in the afternoon, get feedback from other teams and instructors in the mid-term design presentation.

Short explanations, long build time. If stuck, reopen the Day 3 (document-based design) and Day 5 (backend structure) pages.
Today's Schedule References

Project Week · Day 7

Build in the morning · talks and discussion in the afternoon

Adjust times to fit your team. Run the afternoon talks with the timer in presentation mode below.

AM Morning · team project focus

10 minStand-upShare yesterday's decisions · today's goal · blockers
60 minCore flow designUSER_FLOW · wireframes · states (normal/empty/error)
70 minWrite specsScreen specs · DATA · API · trace table (Day 3 way)
40 minAI design review/plan-design-review · /plan-eng-review → DECISION_LOG
20 minPrepare talkStructure the 5-minute talk · fix the screens to demo

PM Afternoon · mid-term talks · design review and discussion

5 min per teamMid-term talkProblem · core flow · structure · risks
3 min per teamQ&A1 good point · 1 question · 1 suggestion
15 minWhole-class discussionShared risks and cutting scope
30 minApply feedbackSort into keep/change/hold → tomorrow's build plan

Briefing · 10 min

Today's short guide slides

Keep explanations under 10 minutes and move straight to team work. Move with ←/→; N key for lecture notes.

Day 7 mission

In the morning finish the design,
in the afternoon get feedback

Today isn't a day for lots of code. It's the day to lock the design in docs so tomorrow's MVP build doesn't wobble.

MorningFinish the designFlow · screens · data · APIAfternoonGet feedback5-min talk · 3-min Q&ABefore leaving: tomorrow's build order in writing!
Morning · BuildDetailed design of 1 core flow
Morning · SpecScreen · data · API specs
Afternoon · Review5-min mid-term talk + 3-min Q&A
Afternoon · DecideConfirm the feedback plan
Core user flow

Exactly one core user flow

Don't design many features shallowly; design the most important flow deeply, all the way through.

Start screenOpen the QR attendance pageKey actionChoose name → check inCheck result"Checked in 09:02"Done · nextShows on dashboardFailure · recoveryDuplicate check-in · network drop → try againBack to the flow after recoveryExample: Project Day QR attendance service · design one flow including the success path + failure and recovery path
Analogy · Borehole

One deep borehole beats many shallow holes

Water (user value)✗ 6 shallow holes — 6 features a little eachNo water anywhere= no flow that works end to end✓ 1 deep borehole — one core flow all the wayScreensDataAPIExceptions · recoveryWater comes out!= a demo you can show every day
Design package

The design package to finish today

USER_FLOWSteps · statesScreen specsUIDATA · APIFields · requestsLAYER_MAPRule · WorkflowTRACEABILITYREQ→TESTDECISION_LOG — decisions, reasons and exclusions for every step
USER_FLOW.mdSteps · screen IDs · states
Screen specsPurpose · info · actions · next state · acceptance criteria
DATA · APIFields · state transitions · request/response/error
TRACEABILITY.mdREQ → UI → DATA → API → TEST
LAYER_MAP.mdRule · Policy · Workflow location per REQ (Day 5)
DECISION_LOG.mdDecisions · reasons · exclusions
AI review loop

Use AI first as a reviewer

No code at the design stage. Find gaps with gstack; the team makes the decisions.

/office-hoursRe-check/specSpec/plan-design-reviewScreen gaps/plan-eng-reviewStructure gapsTeam decidesAcceptedUpdateReject→ DECISION_LOGDesign stage: "don't write code yet"
Mid-review pitch · 5 min

The mid-term talk is 5 minutes · 4 scenes

It shows the design's reasons and risks, not how finished it is.

Problem · 1 minWhose pain, and what painCore flow · 2 minWith wireframesStructure · 1 minData · API · layersRisks · 1 minUncertainties + request for help
1 min · ProblemWhose pain, and what pain
2 min · Core flowWalk through with wireframes
1 min · StructureData · API · layer placement
1 min · RisksThe most uncertain point + request for help
Taking feedback

Sort feedback, then decide

You don't have to apply all feedback. Decide, with reasons.

Audience team: 1 · 1 · 1 format1 good pointQuestion 11 suggestionPresenting team sortsRetentionRecord the reasonUpdateApply before tomorrow's buildHoldAfter MVP · record the reason
KeepOur design is right — record the reason
ChangeApply before tomorrow's build
HoldAfter the MVP — record the reason
1 / 7
LECTURE NOTE

Done Criteria

Today's Done Check

Put this on the team screen and tick items one by one. Ticks are saved in this browser.

Presentation & Discussion

Presentation Mode Settings

Set the team order and times, then press Start presentation mode to open a full-screen stage and timer for the projector.

Presentation order

Enter one team per line in the format Team name | Project name.

Time settings (min)

Yellow 1 minute before the end · red with a chime at the end; overtime keeps showing with +.

  • SpaceStart / pause
  • →←Next / previous step (talk → Q&A → next team)
  • RRestart timer · +- adjust 30 sec
  • DWhole-class discussion · BBreak/waiting screen · FFull screen · EscClose

10-Day Course Navigation

Click the buttons above to go to the Day 1–10 learning pages.

Video Library

Day 7 reference videos

Pick only the topics you need during team work. Videos are public YouTube videos.

Related YouTube Videos
  • Design · wireframes
  • 1. How to Make a UX User Flow with an Example in 5 MinutesDrawing user flowsEN
  • 2. How to Create Your First UX Wireframe in 10 MinutesYour first wireframeEN
  • 3. Design a Mobile App Wireframe in Figma (Beginner)Mobile wireframes in FigmaEN
  • 4. Why you rewrite code when you ask AI for code firstDesign first, code laterKR
  • Data · API design
  • 5. 9 Must-Know REST API Design Principles for DevelopersAPI design principlesEN
  • 6. 4 Simple Tips for Better REST API DesignShort API design tipsEN
  • MVP scope · feedback
  • 7. Michael Seibel - How to Plan an MVPSetting MVP scope (YC)EN
  • 8. The easy and effective way to run a usability testChecking your design with usersEN
  • 9. Demo day pitch: make your 5 minutes memorableMake a 5-minute talk memorableEN

If playback is restricted by the uploader, open it directly on YouTube.

Day 7 · Daily Feedback

Today's Course Satisfaction Survey

After Day 7 class, please answer a short survey. Your answers help us improve the next class and the course.

Open Day 7 SurveyJoin with the button or QR code
Day 7 Daily Feedback Survey QR codeSCAN TO OPENNigeria AI Training · Day 7