A redesigned dashboard that tells couples what to do next

The app’s first screen mirrored the website, page by page. We turned it into a guide, where every suggestion is one tap from doing it.

The new Your website dashboard: the website preview, then Explore designs, Add a cover photo and Define your dress code.
when
Oct 2026
team
Me (senior product designer)
Content Designer
Product Manager
Engineering Manager
iOS engineers
focus
iOS, interaction design, content design, A/B testing

Our biggest complaint from couples: “It’s hard to use”

Ease of use was the biggest problem we were solving this year, and couples told us so again and again. On iOS, the first thing they saw after making a website was a Manage page that listed everything on it, page by page, with no hint of where to start.

A guide, not a mirror

My idea was to lead with what to do next. A few suggestions sit at the top of the dashboard, and each one is written for the guests, not the setting: not just “Define your dress code” but “Help guests figure out what to wear (and feel fabulous!)”.

From a list of pages to a next step

The old page showed every setting and every page, in order. The new one opens on the website, then two or three things worth doing next, then the pages.

The old Wedding website page, scrolled whole: design, URL, privacy, publish buttons, then every page with its own Edit link.
BeforeEvery page and setting, in order
The new Your website dashboard, scrolled whole: the preview, three suggestions, the pages, RSVP, settings, and Publish website pinned at the bottom.
AfterWhat to do next, up top

One tap, straight into editing

Every suggestion opens the exact flow it describes, not a page to go hunting on. Save it, and you’re back on the dashboard, where the card says it’s done and takes you right to the page to see your work.

  1. Tap a suggestionon the dashboard

    A suggestion card: Add your wedding Q&A. Give guests a home for any questions about your events.
  2. Write a question and answerthe form opens straight away, nothing to find first

    The Add a Question form: a question field and an answer field.
  3. Back on the dashboardthe card says it’s done, and links to the page

    The same card, done: a green check, Question added! Preview and add more.
  4. See it on the sitethe Q&A page, ready for guests

    The Q&A page on the wedding website, with two questions and their answers.

Safe to play around

Two goals pulled against each other here. I wanted couples to treat their site as a draft they could play with, without worrying who might see a half-finished page. But a site nobody publishes doesn’t help anyone, and publishing was one of the numbers we most wanted to move. So the button to publish is always within reach, and the reassurance sits right beside it.

The bottom of the dashboard: Guests can’t see your website yet, and a Publish website button pinned above the tab bar.
BeforeNot published yet: guests can’t see it
The bottom of the published dashboard: a Share website button pinned above the tab bar.
AfterPublished: Share website, same spot

A dashboard that grows with them

As couples finish things, the suggestions move on to what’s next. Once the website is published, they step aside for the pages and settings.

The new Your website dashboard: the website preview, then Explore designs, Add a cover photo and Define your dress code.
Just startedDesigns, a cover photo, a dress code
The dashboard with three new suggestions: Tell your love story, Add local hotels, Add things to do.
Getting thereTheir story, hotels, things to do
The published dashboard: the preview, then the pages, with no suggestions.
PublishedOut of the way

It won, and it’s rolling out to everyone

We ran it as an experiment from August. By October it had won, with a large lift in publish rate and key editing metrics, and it’s rolling out to every couple.

more at The Knot
The first-place team in the SeatAgent hackathon

Hackin

TK hosted a 2 day hackathon where the goal was to find ways to use AI that will make life easier for ourselves or our users. It was rewarding because we went after a true, documented pain point in event planning and built something that fit naturally in the product (which was important to me because I complain about useless AI features all the time and I didn't want to be a hypocrite lol).

I don't think I can share too much more right now, but I'm proud of our team and am hoping we'll make it a reality soon so you can check it out live!

thanks for stopping by

got a project in mind? say hi