AHF Products
Leading website work across 15 brands.
I’m the main coordinator for website work across 15 AHF brand sites. I set the submission requirements, work through priorities with marketing and leadership, and keep requests moving through development, requester notification, and closure.
The team delivered more work, faster.
Complete product data became a requirement.
Requests often arrived without the product data needed for the website. The web team absorbed the extra work: filling gaps and reformatting what had been submitted.
I defined the required product information and worked with marketing managers to use brand-specific submission templates. Incomplete requests now go back to the requester before development starts, with the missing information identified.
Launch timing and business impact set the priorities.
I work with marketing managers and my manager to decide what moves first. We consider launch timing and business impact, then check whether the request has the content and data needed for development.
- 01Launch timing
- 02Business impact
- 03Submission completeness
Requests now end with QA, notification, and closure.
Development handles the QA pass. I then notify the requester and close the Asana task. That gives each request a clear endpoint and lets the person who submitted it know the work is complete.
Individual notifications close each request. A weekly release email gives marketing a view of changes across the brand websites.
Marketing knows what to submit and what happens next.
Marketing managers have clearer requirements for submissions and more visibility while the work is underway. They know what to provide and have a clearer idea of when it will be done. I coordinate that process alongside product launches, routine updates, and the larger website redesigns.
PIM is the next data milestone. Until then, the templates and submission review give us a consistent way to get product information ready for the websites.