I led the design of KICK’s Stream Calendar, creating a native scheduling experience for creators and a reliable way for viewers to discover upcoming streams. Partnering with Creator Tools 🧰 and Engagement.
Role
Lead designer, Creator Tools and Engagement
Collaboration
Product, Engineering, Design, Branding, Marketing, Partnerships, and Leadership
Timeline
1 Month
Platform
Desktop , Mobile Web and Mobile App
Giving creators a clearer way to communicate upcoming content supports KICK’s engagement goals by helping viewers plan return visits. Adoption, retention, watch-time, and revenue effects require separate measurement and are not claimed here.
A native scheduling destination
Version 1 introduced a dedicated channel calendar where creators could publish and manage upcoming streams. It added an on-platform alternative to communicating schedules through third-party tools or profile text.
Visibility for viewers
Viewers could find upcoming streams directly on a creator’s channel, giving them information to plan when to tune in.
Positive public creator feedback
Responding to KICK’s release roundup, Audrey Brown, who described building her community on KICK, called Stream Calendar a “HUGE win for creators.” She specifically welcomed its contribution to consistency and discoverability.
Schedules existed, but the channel lacked a dedicated destination
Creators were already finding ways to tell their audiences when they planned to stream. Some used third-party platforms; others placed schedule information in their KICK About section. The gap was a dedicated place within the channel where creators could maintain those plans and viewers could consistently find them. Fragmented communication also left uncertainty about how many viewers knew when the next stream would happen. For creators, the opportunity was to make scheduling part of managing their channel. For viewers, it was to make upcoming content easier to locate. For KICK, it was to strengthen the connection between creator planning and audience engagement within the platform. The team wanted to move quickly. We needed a practical first release that also accounted for recurring schedules and changes to existing events.
Partnerships conducted extensive feedback sessions with streamers to identify the gap. Product Management, Design, and Leadership reviewed that feedback together and narrowed it into requirements.
My role was to translate those requirements into an experience that worked for both the creator setting up a stream and the viewer looking for upcoming content.
The feedback and team discussions focused the work on two connected needs: helping creators maintain their schedule and giving audiences a reliable place to refer to it. Those needs shaped both the calendar presentation and the creation flow.
Choosing a monthly view that brought stream states together
We explored different ways to present the schedule, including calendar and card views. A conventional seven-day layout raised questions about whether it suited KICK’s context and the importance of upcoming content. The team worked through the presentation, individual stream states, and recurring-event behaviour. We ultimately shipped a monthly calendar that brought the different states together. The challenge extended beyond choosing a grid. The calendar had to communicate what was happening across the schedule while keeping upcoming streams understandable within the wider month.
Revealing recurring-schedule inputs as they became relevant
Scheduling required several inputs, and the team initially proposed a longer form. I recommended progressive disclosure so creators would see additional information in response to their choices. For recurring streams, the inputs changed according to the selected dates, number of streams, and end date. This made the form responsive to the schedule the creator was building, with the aim of reducing the amount they needed to consider at once.
Separating an edited occurrence from its original series
Recurring schedules introduced a consequential scenario: a creator could set up a daily series, then edit one event without intending to change the rest. I designed the behaviour so the edited occurrence could separate from its original recurrence pattern, preserving the remaining events. The changed event could then become the starting point for a different recurring schedule. This treated an exception as a deliberate change while maintaining the creator’s original plan for the rest of the series.
Version 1 covered the agreed PRD requirements:
- Creating, editing, deleting, and rescheduling streams.
- Managing those actions within recurring schedules.
- Sharing a stream.
- Mobile optimisation.
- Feature introduction and education.
I designed the calendar and full scheduling flow, accounting for the relationship between the calendar view, creation inputs, stream states, and recurring-event behaviour.
The work progressed through repeated stakeholder discussions, presentations, design team reviews, and design QA. I collaborated with Product and Engineering alongside Branding, Marketing, Partnerships, and Leadership to align the experience and prepare it for release.
The V1 design flow was completed in approximately one month. KICK subsequently shipped the feature and included it in its public August release roundup.
Validation during the project included internal reviews, stakeholder presentations, design team feedback, and design QA.
The public release and creator response establish that the feature shipped and that a creator recognised its value. They provide qualitative evidence alongside the delivered experience.
Recurring-event behaviour deserves attention early
The creation form was only part of the problem. Editing one occurrence could affect an entire schedule, so exception handling needed to be considered alongside the primary flow.
Familiar patterns still need to fit the product context
Exploring calendar and card presentations helped frame the experience around KICK’s context. The final direction needed to account for upcoming content and stream states.
Complexity can be revealed progressively
The recurring-schedule flow showed how inputs could adapt to creators’ choices. Progressive disclosure offered a way to retain scheduling capability while limiting the information presented at each step.
Let's work together
Good products rarely need more complexity.
They usually need someone willing to understand the problem deeply enough to remove it.
If you’re building something ambitious and need a senior designer who can move between product thinking, interaction, craft and delivery, I’d love to talk.
Based in Melbourne, Australia
Full Australian working rights
Open to senior product design opportunities and selected contract work.
