All of the above. I’ve worked across web apps, native iOS/Android products, and websites. The sprint is focused on clarifying the core experience and decisions, regardless of platform so teams can move forward with confidence.

I lean heavily on async collaboration and share work early and often. We’ll start with a longer kickoff to establish clear alignment up front, then use async updates (often via short Loom-style recordings), quick check-ins, and focused syncs when they’re actually useful. This keeps momentum high without unnecessary meetings.

Validation is lightweight and tailored to the context. Depending on the product and timeline, it may include qualitative user interviews, unmoderated feedback on a prototype, quick surveys, stakeholder review, or heuristic evaluation. The goal isn’t exhaustive research, it’s early signal to surface risks, assumptions, and areas to refine before building.

After the sprint, teams can take the outputs and move directly into build, or continue working together through a follow-on project or fractional design partnership. The sprint is designed to stand on its own, but it often clarifies what the next step should be.