PowerAdvice is far enough along that I need help keeping people oriented. I need your eye on the front end, the CMS, and the way we explain what is done, what is next, and what needs a call.
Doug is the taste and trust filter. His feedback has driven the visible product: right rail behavior, masthead wordmark and tagline, channel templates, Ask controls, Purple Wonderland, sponsor divider, and the active-cursor question.
When Doug says something feels off, turn it into a concrete design decision, a before/after, and a small PR.
Suzanne needs the clean version of the project: what is ready, what is parked for a call, what still has risk, and whether the path to July 1 is credible.
Do not give her repo noise. Give her timing, scope, confidence, and the decision that needs to be made.
Jakie is part of the channel and marketing read. In the June 15 deck, the team needed Jakie and Tory to lock the 12 launch channels, settle Media vs Podcasts, and keep sub-topics as tags instead of new channels.
For Pascal: help make channel, newsletter, sponsorship, and launch-language decisions easy to review.
Tory's notes have already turned into shipped UI work: the Ask gradient and palette, labeled rail tabs, readable date, no visible Sponsored label, Podcasts taxonomy follow-through, and practical CMS/ad workflow questions.
Treat Tory as the day-to-day operator check. If the CMS or ad setup is confusing, she will feel it first.
LeeAnn sits closest to the editorial production reality: research, contributor communication, contributor engagement, article review, and the repeated work that has to happen after launch.
Use her lens for contributor records, article cleanup, source accuracy, and whether the CMS makes repeated editorial work easier.
Howard's lane is the migrated library: locked channels, article master, source URLs, metadata, redirects, search traffic, and MCP review across the full corpus. The June 15 deck put the migration handoff squarely in his lane.
Do not mix Howard with editorial taste. He needs stable taxonomy and reliable tooling so he can work the sheet end-to-end.
Take the pile of notes, tickets, previews, and PRs and turn it into the version people can act on.
Type, spacing, ads, templates, Ask, sponsors, mobile polish.
IA, scanning, tables, forms, empty states, workflow clarity.
What it is, what it is not, and what we should be careful about.
Keep them small. Attach the preview. I can review and merge whenever.
I own migration and the next ad review. You can still make them understandable.
