Don't Let Your RFP Become An RFPoo

All too often, web projects are destined to fail before they begin. Perhaps requirements are too vague or too rigid; perhaps hyper-focus is put on the wrong areas of the project; or perhaps there is a struggle over expertise, not allowing for honest, collaborative client-vendor consultation. The results of these pitfalls can range from months of lost time and effort to hundreds of thousands of wasted dollars.

Trinity University, in collaboration with their agency partner, ImageX, has found a way to put web projects on a rocketship toward success, straight from the get-go: they’ve transformed the traditional Request for Proposal (RFP) process.

“But how?” you may ask. Take a tour of their experience here: https://slate.adobe.com/cp/d0XxK/

These partners propose that the answer includes extensive preliminary research, transparency, and collaboration. Through this case study, we will:

• review the most common RFP approaches (and their unintended consequences)

• examine the trials and tribulations of Trinity’s traditional RFP process

• discuss how we changed the process for two separate web projects and found success along the way

Audience members will be engaged through a series of Q&As, and they will take away best practices that can be applied to any organizational structure, regardless of traditional procurement rules. Any web project owner or contributor who has experienced poor results from a traditional RFP process or who is anticipating future web projects will benefit from this presentation.