Skip to content
Alan Lindsay ConsultingEmail

Organize

Set up how the team works

Process and methodology

A working rhythm that separates strategy from the daily queue.

When strategic work and bug reports compete in one backlog, both lose. I design an operating rhythm that fits the team you have: how work comes in, how it is prioritized, and how often plans are revisited.

The engagement ends with the process running and written down, so it keeps working after I leave.

Engagements are scoped as statements of work.

Alan has a real skill in helping to cut through the noise and focus on delivering value.

Brian LeachLead Designer, Design Systems, Collibra · Via Experian

His ability to map out larger projects into smaller, bite-sized chunks was no small feat.

Chris FoisyStaff Product Designer · Via Experian

You might need this if…

  • Urgent requests keep displacing planned work.
  • No one can say when the next strategic project will actually start.
  • The backlog has grown past the point where anyone reads it.

Selected examples

  • OneShare Health. Designed and codified the product development playbook: weekly triage to inbox zero, Tactical Mondays prioritized by stakeholder dot voting, and six-week strategic cycles with two-week cooldowns.

  • Circadence. Brought alignment to an engineering-centric organization through its ticket system: every business initiative broke down into epics, stories, and tasks, so engineering work traced back to a business goal instead of stopping at the epic.

Product-org stand-up

Product discipline for a company that has been shipping without it.

Some companies ship on engineering instinct until the gaps start costing real money. I set up the practice: how product decisions get made, who makes them, and the rituals that keep engineering tied to strategy.

You own the practice when the engagement closes. It is built to be run by your people.

Engagements are scoped as statements of work.

Alan bridges gaps in organizational structure to make everyone more effective.

Roman BercotStaff Product Designer, ServiceNow · Via Experian

He turned an influential technology leader from a UX skeptic into an eager supporter who funded a UX team and design system.

Nick SaundersFront-end engineer, design systems · Via Experian

You might need this if…

  • Engineers decide what gets built because no one else does.
  • Features ship, but no one can say which business goal they served.
  • Requests arrive from every direction with no single place to weigh them.

Selected examples

  • Circadence. Stood up product discipline from zero inside a siloed engineering culture and tied engineering work to strategic initiatives instead of disconnected tickets, cutting hundreds of hours of wasted effort.

  • OneShare Health. Stood up product practice at a company with no product or engineering organization: design ideation, user research, mockups, stakeholder review, requirements synthesis, and product-focused development cycles that turn designs and concepts into workable engineering stories.

NextDesign and buildDesign it and build it