OpenPages was acquired by IBM in Oct. 2010. Though the product was highly functional it was experientially outdated. This introduced significant technical, relational and process-centric challenges for my team and I to overcome on our way to a complete redesign.
Product
—
Despite a technically deep and highly functional product with a strong user base, OpenPages was more than showing its age by the time I joined in 2017. User experience-wise, there were numerous usability as well as performance challenges to overcome. It was clear there were no easy fixes for this - a holistic solution was needed.
—
Despite a technically deep and highly functional product with a strong user base, OpenPages was more than showing its age by the time I joined in 2017. User experience-wise, there were numerous usability as well as performance challenges to overcome. It was clear there were no easy fixes for this - a holistic solution was needed.
Relationships
—
Having joined in 2017, my team and I were all new to OpenPages and had no history working with the existig team. The design team prior to ours famously clashed with product management and was ultimately dissolved. We would need to create new bonds, build trust and give ourselves a solid foundation before anything else.
—
Having joined in 2017, my team and I were all new to OpenPages and had no history working with the existig team. The design team prior to ours famously clashed with product management and was ultimately dissolved. We would need to create new bonds, build trust and give ourselves a solid foundation before anything else.
Process
—
Our team was newly formed, comprised of long-time OpenPages folks and brand new designers. We’d never worked together and had no cohesive process to speak of. As we built relationships, we had to build our new cross-disciplinary new process at the same time.
—
Our team was newly formed, comprised of long-time OpenPages folks and brand new designers. We’d never worked together and had no cohesive process to speak of. As we built relationships, we had to build our new cross-disciplinary new process at the same time.
Melbourne, AU — Client Workshop![]()
Durham, NC — Client Workshop![]()
From the beginning we used Enterprise Design Thinking and workshops as a means of aligning ourselves across disciplines, planning our releases and our user research.
From the beginning we used Enterprise Design Thinking and workshops as a means of aligning ourselves across disciplines, planning our releases and our user research.
Boston, MA — Client Workshop![]()
We regularly ran such team-wide workshops to establish scope and vision for our releases, which we invited our stakeholders and users to engage in.
We regularly ran such team-wide workshops to establish scope and vision for our releases, which we invited our stakeholders and users to engage in.