Sloan Miller

Sloan Miller is a Philadelphia based creative and technology industry veteran with expertise in operations, strategy, business development, managing marketing, digital, and development projects, and leading teams.

Sloan is an operations strategy consultant and freelance project manager. Previously he was the director of operations and outreach at P’unk Avenue, plus founded and lead the project management department at The Archer Group.

Over the last 13 years, Sloan has guided complex eCommerce, mobile applications, campaigns, responsive websites, and content management system projects of all shapes and sizes, across many sectors, for a range of large and small international, regional, and local clients. He has a reputation for building strong client relationships, increasing retention, and finding creative solutions.

Sloan’s passion for community engagement and mentoring extends beyond the Philadelphia creative and technology industry. He is a founding member of a DPM Philly, and has spoken at several events on the topics of effective management of teams, projects, and process, teaches a digital operations and project management course at the University of the Arts, and has attended the past two DPM Summits. Follow him on Twitter @PMOwned.




Come On...It's in the Requirements

October 13th | 1:30 PM

Let’s be super honest… gathering requirements and maintaining them throughout a project is a royal pain. And to top it all off, when the documentation is complete you always wonder if anyone really reads it. 

Clearly defined and cataloged requirements are a vital component of most projects. They are discovered, elevated, and changed throughout the entire project. They impact everything from user experience and information architecture, to design and development. Not to mention they are core to successful completing quality assurance testing and pre-launch procedures. 

Whether you are working in an environment where requirements are rarely documented (sometimes strategized and conveyed in real-time) or if your 100+ page IEEE specifications book was finished months ago, fluidity in requirements for digital projects is unfortunately somewhat necessary. Ambiguity can never be entirely removed, but excessive amounts of it kill a project's timeline, budget, and potential for success.


  • Where requirements typically come from and how to be on the look out for them.
  • How to identify different types and scale of requirements.
  • Some simple and easy ways to record and catalog requirements.
  • Some tips on how best to maintained requirements as they continue to evolve.
  • A discussion of some examples of what can go wrong when requirements aren’t properly maintained or if they are ignored.