Design team wiki

We need a single design team wiki that new hires can use on day one. Gather the latest brand guidelines, component library links, current project briefs, and the names of three people to ask for design decisions. Put an introduction page titled How our design team works, a page for Design standards with the color and type specs up top, and a Projects index that lists active work and owners. Make Hiring and Onboarding pages and a Friday deadline to review completeness with Priya, the design lead.

Before I open this wiki to the whole company, make it simple to use for non-designers. Move the quick answers—who owns what, how to request a mock, and where to find assets—onto the home page. Highlight the component library link, surface the approved color palette as an image, and flag any pages missing owner or last-updated date so reviewers can approve quickly.

I published a draft wiki for the design team and pinged Slack, but only one person commented and the design lead hasn’t opened it. I’m worried it’s missing the right practical details or someone will say it’s the wrong format. What are the likely reasons it’s getting ignored and what single change will make reviewers open it this week?

We repeatedly get the same three questions from new hires: where to get the latest components, who approves visual changes, and how to request time on the roadmap. That wastes senior designers’ time and makes onboarding clunky. Which two habits should we change in our wiki and team routine so those questions stop, and what immediate step enforces the change for the next hire?