Mobile app for team event creation & participation

GoodTeam was designed with a friendly, low-friction personality — warm but professional, the kind of tool people open without feeling like they’re “using corporate software.” The visual language leans on soft shapes, generous spacing, and a confident color palette that signals approachability without sliding into childishness. Every microinteraction was designed to confirm what just happened, so users always know where they are and what their last action did.

The app’s structure is built around two modes that mirror how people actually use event apps in real life — you’re either the person creating something or the person responding to it. Organize mode gives hosts a fast path to set up an event, invite participants, and track responses. Attend mode gives team members a clean feed of events they’ve been invited to, with one-tap RSVP and the option to dive deeper if they want context. Switching between modes feels like switching contexts in your head, not navigating a menu.

Before designing a single screen, we ran a full SWOT analysis of the GoodTeam concept against the existing landscape of corporate event tools. The strengths were clear — a tightly defined use case (internal team events, not public ticketing) and a clean opportunity to compete on simplicity rather than feature count. The weaknesses were honest too: a crowded market, low switching incentive for teams already using Slack or Outlook for the same job, and the constant risk of scope creep turning the product into yet another over-engineered platform.

The opportunities shaped the entire design direction. Most competitors treat event creation as a heavy, form-driven process built for external audiences — conferences, ticketed events, public meetups. Internal corporate events have completely different dynamics: smaller groups, recurring patterns, lower formality, faster decisions. Designing for that gap meant we could strip away most of what makes traditional event apps feel bureaucratic.

The threats we documented — feature bloat pressure, calendar app competition, low engagement after initial novelty — became explicit constraints during design. Every feature proposal was tested against them: does this solve a real internal-event problem, or are we copying Eventbrite? That filter shaped what made it into the final product and what stayed out.

We mapped the full Business Model Canvas during the discovery phase to make sure design decisions stayed aligned with how the product would actually create and capture value. Customer segments were defined narrowly — mid-sized companies with distributed or hybrid teams, where coordinating internal events across locations is a real operational pain. Value propositions focused on speed and clarity: making event creation faster than writing a Slack message, and RSVP simpler than replying to an email.

Key activities and resources translated directly into product requirements — the app needed to work offline for participants, sync reliably across iOS and Android, and integrate cleanly with existing calendar systems without forcing teams to adopt yet another tool. Channels and customer relationships informed the onboarding flow: GoodTeam had to be usable within the first event a team organized, otherwise it would never reach the second.

The revenue and cost sides of the canvas guided what we deliberately didn’t design — no in-app payments, no premium feature gates, no analytics dashboards beyond what an HR coordinator actually needs. Keeping the canvas visible throughout the design process kept the team disciplined about scope, which is half the battle on internal product work.

The interactive map surfaces events geographically — useful for hybrid teams or larger companies with multiple offices. Users can spot what’s happening near them, filter by date or category, and tap directly into event details. The map is a discovery layer, not a primary navigation element, which keeps it useful without making it the centerpiece.

Inside event creation, the flow guides hosts through the essentials first — name, date, location, participants — and progressively reveals optional fields like agenda, notes, or attachments. This means hosts can publish a basic event in under a minute, or take the full path when the event genuinely needs more structure. The same form works for both, which removes the choice fatigue of “simple vs. advanced” mode toggles.

Each event has its own dedicated chat thread, scoped to participants and tied to the event lifecycle. Conversations stay focused on the event itself instead of bleeding into general team chat, and once the event is over, the thread archives automatically. It’s a small detail, but it solves the most common complaint about team apps — that messages from last week’s lunch are still pinging you a month later.