← Back to overview

Process

How we work, decide & ship

Rituals, frameworks, and guides that keep the product sharp and the team aligned. Tenets first — then the practices that turn them into shipped work.

EXISTING

Tenets

These four principles are the foundation of every pattern and interaction at N2ITION. They are deliberately placed first and largest so they are impossible to miss while scrolling.

Flexible

Use it how you want to use it. The system bends to your workflow, not the other way around.

Accountable

Visibility to your Team. Every action and decision is traceable and transparent.

Discoverable

Uncover relationships. Data and context surface naturally so you can see connections.

Empower

Actionable insights for decision making. Information leads directly to clear next steps.

FROM SOURCE

Design Process (adapted)

From problem framing through prototypes, research, and handoff. Craft detail, patterns, and IA live under Product Design.

See Product Design → Components & Patterns · Information Architecture
EXISTING

Rituals

UX is a shared resource, not a 1:1 pairing service. The work source of truth is GitHub Projects. The biweekly is UX for Devs 101 — 25–30 minutes. These pages are the human reference. Pilot through 30 September 2026, then keep the cadence if it holds.

How a story moves

  1. GitHub Project — file a UX story. User, job, and success are required. If those are blank, do not build.
  2. Needs discovery → In FigJam — duplicate the intake board. Write questions with an owner and a date.
  3. Ready for build — must / should / not are on the issue. AI-dev notes name the playbook patterns to reuse and what not to invent.
  4. Preview / PR → In review — walk the job. Empty, loading, error, and permission-denied exist.
  5. Audit → Done — critique against this playbook. Fix what blocks the job; file the rest.

101 · Lesson 1

The user is the ticket

Outcome, not control. Fill User / Job / Success on the GitHub issue.

101 · Lesson 2

Requirements live on the issue

Must / should / not, owned questions, FigJam intake.

101 · Lesson 3

Do not invent, then walk the job

Playbook reuse and a 10-minute critique of their preview.

Stay ahead

UX works one cycle in front of build. Not in one person’s editor.

  • Pull the next Project items before the session. Write questions on the card the same day they appear.
  • Pre-fill the FigJam. Link the patterns on Components & Patterns.
  • Do not take ad-hoc 1:1 “can you jump in” as the default. Point at the card or the next session.
  • After a session, UX status and questions are updated within 24 hours.
COMING SOON

Coming soon

Product Triad

How PM + Design + Engineering own outcomes together.

Details coming soon · Todd

Demo tips

Telling the story, showing the data, and handling the room.

Details coming soon · Jess

N2 Labs

Experiments, spikes, and wild ideas that may become real.

Details coming soon · Todd