Skip to main content
Learn.

Catalog / Methodology

Design methodology
for serious work.

A practical operating system for Jambo trainees in Arusha, Tanzania: understand the context, structure the problem, craft the interface, validate the work, and improve it after launch.

Jambo standard

Raise the baseline, not only one screen.

Learn is part of Jambo's larger work: building practical technology capability from Tanzania for African teams and markets. The goal is not to memorize UI words. The goal is to make design judgment teachable, repeatable, and useful in real products.

Context beats decoration

A polished layout that ignores the user, market, or device context is not strong design. Visual decisions should trace back to the actual job the product must do.

Systems beat screenshots

Top-tier designers create reusable rules. A page should teach the next page how to behave through shared grids, tokens, components, copy patterns, and states.

Evidence beats opinion

Reviews should be tied to goals, constraints, and observed behavior. Taste matters, but it should not be the only reason a decision survives.

Handoff beats handover

A file dump is not enough. Handoff needs explanations, edge cases, assets, responsive behavior, and the quality bar developers should test against.

Working model

Six stages from context to improvement

1

Input

Observe the real context

Start with the people, place, device, network, language, business model, and constraints around the work. Good design begins before the screen.

  • Visit the current product, site, or workflow before sketching alternatives.
  • Name the primary audience, their goal, and the environment where they will use it.
  • Record constraints such as content gaps, launch date, budget, maintenance owner, language, bandwidth, and device mix.
2

Judgment

Frame the problem

Turn broad ambition into a sharp design problem. The team should know what success means and what tradeoffs are acceptable.

  • Write one problem statement in plain language.
  • Define the success metric, decision maker, risks, and non-goals.
  • Separate user needs from stakeholder preferences so feedback stays useful.
3

Architecture

Structure the system

Before visual polish, decide how information, navigation, page sections, and user journeys fit together.

  • Map the sitemap, user flow, content hierarchy, and primary calls to action.
  • Use wireframes to test order, grouping, density, and responsive behavior.
  • Remove sections that do not help users understand, compare, decide, or continue.
4

Execution

Craft the interface

Apply typography, grid, color, spacing, imagery, components, and motion as one system. Craft is how strategy becomes usable.

  • Build from reusable styles: type scale, color roles, spacing, radius, shadow, and component states.
  • Design mobile, tablet, and desktop as related layouts, not one stretched screenshot.
  • Make every major component handle default, hover, focus, loading, empty, error, and success states when relevant.
5

Proof

Validate under pressure

Top-tier work survives real checks: unclear copy, missing data, slow devices, small screens, keyboard use, and launch deadlines.

  • Review accessibility, contrast, keyboard focus, form recovery, metadata, speed, and responsive layout.
  • Test the work on a real device or realistic viewport before handoff.
  • Use feedback scripts that ask whether the design solves the goal, not whether people like the style.
6

Launch

Hand off and improve

A design is not finished when the file looks good. It is finished when another person can build it, test it, launch it, and improve it.

  • Package component states, responsive notes, assets, copy, analytics events, and acceptance criteria.
  • Confirm ownership for content, updates, security, backups, support, and post-launch measurement.
  • Return after launch with evidence and update the system instead of starting from zero.

Training loop

How trainees should practice

1

Study

Read the term, inspect the diagram, and connect it to a live interface.

2

Rebuild

Recreate a small section with the same intent but cleaner structure.

3

Explain

Say why each spacing, type, color, and component decision exists.

4

Review

Run the work through accessibility, responsive, state, and handoff checks.