Project Purpose and Objectives

What started as a routine policy manual became something much bigger to me. It became a comprehensive, living handbook for the New Student Mentoring program; a resource that would be referenced by nearly 200 employees. The goal wasn’t just to document rules. I wanted to build a resource mentors would actually reach for day after day. At the heart of it all was a simple question: why does the work they do each day matter?

Every page was built to help mentors connect their daily tasks back to the program’s real mission: Empowering students to belong on campus, reach their goals, and lead those around them. Alongside that, the project set out to give the department a clear professional identity and equip mentors with a practical tools they could put to use immediately. The end goal was ambitious but concrete: a polished, printed resource ready to train hundreds of employees.

The Project: Deliverables and Outcomes

The finished handbook is a multi-part resource, with each piece serving a clear purpose:

Employee Growth and Development Guide: This may have been my favorite part. Anchored in the department’s “Belong, Reach, Lead” tagline, I designed this guide with the best research available. It gives employees a visual roadmap for their growth, complete with three tailored evaluation checkpoints, a goal-tracking sheet, and a leadership framework inspired by Simon Sinek’s work. I’m a big fan of his.

Practical Resource Tools: A categorized FAQ section built directly from survey data, and a campus resource guide puts key contact information for student support services right at mentors’ fingertips. It’s almost like a friend that mentors can refer back to anytime they feel stuck.

Visual Communication Design: From custom diagrams and icons to a professional front cover, visual storytelling ran throughout. One standout to me is the dress and grooming guidelines page. It goes past explanation. It has a full-page infographic, swapping dry text for photos of real former employees highlighting images of what to wear, and what to avoid. This instantly became more engaging and more human. It also makes a fun shoutout for long-time employees.

Departmental Framework: The handbook opened not with rules, but with purpose: a dedicated section laying out the department’s mission and vision right from page one. It also indicates the importance of various mentor policies and standard operating procedures built around this framework. This makes the sections on a mentors daily tasks feel more purposeful and clear.

Challenges Encountered

Handbooks have a reputation problem. They tend to be dense, text-heavy, and hard to navigate. Beating that reputation took deliberate, sustained effort on visual design to make information easier to absorb and retain. There was also a real, human problem to solve: new employees consistently hit a “flood of questions” in their first few weeks, which meant rethinking how information was organized and accessed, not just what was included. As the project’s scope grew, keeping it on track demanded real organizational discipline and constant communication. Even in the final stretch, the work wasn’t done. I had to be prepared for last-minute stakeholder requests, like adding page numbers and notes pages. Regardless of this the deadline doesn’t move. Changes have to be folded in right before the print deadline, and cost-risk analysis have to be made. I think I can vouch for my team when I say we made it through the hiccups quite well.

Project Processes

The handbook came together through a structured, iterative “sprint” approach:

Foundational Phase: Everything started with the Growth Guide initially, as this was our most researched and original work. Researching and drafting it first set the visual and tonal language that would carry through the entire document.

Structural Outlining: At the outset of core development, a “living index” was born. It became an in-text outline that evolved and updated in real time as new sections took shape. This made it easy for my team to always see what was added without needing to refer back to a different document constantly.

Content Generation: A full rough script came together before any fine-tuning began, laying the groundwork so that 95% of the handbook’s layout and design could move forward as one unified whole.

Iterative Refinement: This was the grind: heavy cycles of editing and rewriting, working closely with the leadership team to weave in feedback and sharpen every graphic to a polish, that they felt accurately reflected their goals.

Finalization: The last sprint locked in layout decisions, put the finishing touches on the front cover, and secured final approvals before the document headed to the printers. Nothing is more satisfying than holding a finished project in your hands.

Overview of Experiences

This project marked a genuine professional milestone. It became the first time I watched scattered digital drafts transform into a high-quality, printed product used by a large audience. Contributing roughly 95% of the layout and 30% of the rewrites gave the work a real sense of ownership and professional pride. I can’t take all the credit though. It became much more than just me. Working alongside a leadership team and taking in high-level feedback from my mentor pushed the final product to a standard I couldn’t have reached alone. And there was a particular kind of satisfaction in watching employees spot themselves in the handbook’s visuals. It’s proof to me that a standard policy document could become something people genuinely connected with.

Insights and Takeaways

If there’s one lesson that stands out, it’s this: good work is rewritten work. The real progress happens in the refining and feedback stages. Staying willing to improve something even after seeing it dozens of times is what separates decent work from great work. I also learned that design isn’t just decoration; it’s a tool for clarity, capable of reshaping how people engage with technical information. It makes information applied information. Above all, this project reinforced a simple truth: professional work isn’t done for yourself; it’s done for the people who’ll actually use it. That’s the standard I’m carrying into everything I build next. I can’t wait to see what further projects come from this experience.