Kaikasen

Petalstorm 2025

Blooming Ideas: Planting the Seeds for a Global Design Conference

Role

Product Designer

What I did

Product Design, Content Design, Visual Direction, Product Strategy, Quality Assurance (QA)

Team

Ko Nakatsu

Head of Design

Val Poon

Design Lead

Dillon Jenkins

Content Designer

Paul Nguyen

Product Designer

Rishav Kumar

Product Designer

Sowmya Chandra

Product Designer

Timeline

8 days

Tools

Figma
Framer
Discord
Google Analytics

Context

Petalstorm was built on the idea that creative conversations should flourish in an environment designed for exploration. To bring this vision to life, Kaikasen needed a digital hub that would not only serve as an informational resource, but also as an interactive experience that reflected the spirit of innovation and connection.

The Problem

We needed a Minimum Viable Product (MVP) for a website. Petalstorm was brimming with potential having its seeds already planted, yet it needed nourishment in order for people to have an environment where this vision could fully flourish. Its roots were set, brimming with energy and excitement, but had no central home to cultivate its identity — attendees lacked a clear path to connect, register, or engage.

Okay... so what did you do?

I laid the foundation for the product and its strategy, shaping its earliest iterations through research, content, and visual direction. My work helped to establish a strong foundation for an MVP by playing a key role in setting the visual direction and informing strategic decisions early on, crafting a visually cohesive experience that reinforced Petalstorm's identity through meticulously structured content — all while meeting an ambitious timeline.

Outcome

Constraints

Figuring out what tools we do and do not have to grow the garden...

This was the first iteration of Petalstorm, meaning there was no existing brand identity or design system to build from. We had to define a visual direction from the ground up while ensuring it aligned with the conference's values and theme. With limited time, we prioritized clarity and cohesion, creating a design that felt distinctive yet flexible enough to evolve in future iterations.
Our team members were positioned in the following cities: San Francisco, Sacramento, Los Angeles, Seattle, Denver, Indianapolis, Toronto, and Delhi. With a team spread across four international time zones, coordination required intentional communication and adaptability. Asynchronous workflows became essential, and we had to be strategic about scheduling synchronous meetings to maximize efficiency.
The project took place over the holiday season in late December to early January, requiring the team to balance work with personal commitments. Limited availability meant we had to be efficient with collaboration, setting clear priorities and leaning into async communication. Navigating this constraint strengthened our ability to work flexibly while maintaining momentum.
With only 8 days to design a brand identity and launch an MVP of the conference website, speed and decisiveness were critical. We streamlined the process by focusing on core priorities, making quick yet intentional design decisions, and embracing iteration. This constraint pushed us to work with clarity and efficiency, proving that strong design can emerge under tight deadlines.

Prepping the Soil

Maybe sowing it a bit too in the process! :)

Benchmarking

some websites I added to our Figma file because I loved the details and how they made me feel

Ko, our design lead, tasked us with first benchmarking conference websites. Our team made an annotated Figma file with conference websites that we all individually liked, which synthesized the work of me and 3 of my other co-designers who did some initial research in the early stages of ideation.

Planting the Seeds

+ water of course

Defining a Brand Identity

Originally, we considered the word "brevity" or "brev" as keywords contributing to visual and emotional identity, since the conference composed of succinct, 10 minutes talks. Hence — brevity. Though, the team ended up seeing a new vision starting to blossom out of the older one...

envisioning the idea of Petalstorm — impressionable, clean, refined

We then envisioned "Kaikasen," a Japanese word for "the journey of a thousand blooms," for the community name, just like how each individualistic journey of each designer is a bloom in itself waiting to happen. Naturally, the petals unfolded and we landed on the conference's new name — Petalstorm.

Letting it Grow

More watering and basking in the warm sun.

Early Iterations

mid-fidelity wireframes I shared with the team

My wireframes were then aligned with visions from other teammates to build and collaboratively iterate upon.

our (growing) design system

I guided the design system's visual direction, recommending a palette of oranges, off-whites, and beiges to evoke warmth and impression — which were refined by our design lead and reflected in the design system.

Tending and Maintenance

I'll pass on the weeds, thanks.

Quality Assurance

I led QA efforts, ensuring our work remained as polished as possible within our time constraints. As one of the two strongest Framer proficiencies on our team, I played a key role in optimization, alongside copywriting and visual design.

Watching the Flowers Bloom

... and potentially sneezing because of my pollen allergy (worth it).

see it live

The flowers have bloomed for Petalstorm 2025 🌸

Launched in January 2025, the Petalstorm website became a central hub for showcasing key projects and inviting deeper engagement. Designed for both desktop and mobile, the experience emphasizes accessibility and visual storytelling—allowing visitors to seamlessly navigate and connect with the conference's vision.

In just the first three weeks, the site saw:

  • •351 pageviews, with users actively exploring beyond the homepage.
  • •88 unique visitors, signaling early traction with a highly engaged audience.
  • •42.6% bounce rate, showing that most visitors stayed to interact with the content.
  • •an average session time of 2 minutes and 21 seconds, highlighting strong interest and meaningful engagement.

As Petalstorm continues to grow, the platform lays the foundation for an expanding design community, inspiring designers to have more collaborative, creative conversations and push the confines of craft.

Points of Growth

Takeaways🪵

never ever ever.
I've already had previous exposure working with design systems, but I always love learning from people. It makes me a better designer. I think working with a team composed of designers with varying experiences was a unique angle to learn from since designers and devs think about design systems differently. They try to unify that syntax through a common language which I think is beautiful in its own regard.
Personal preference, but I always love seeing what I can make under time constraint to challenge myself. It's a double-edged sword (lol).
back home
© 2026 • Made with ❤️ in Bharat 🇮🇳 | Priyanka Gunjal™ • All Rights Reserved