Problem Statement:
How can we identify and make relevant
technical content easier to discover for
accomplishing goals that guides users to
logical alternatives when content is
absent and enables collection of feedback
to improve the value of technical content?
IBM Advocate
Highly technical understanding of IBM Z
Systems, years of industry experience, and
share IBM knowledge with her customer base.
Learning Perference: Detailed information,
and nitty-gritty details.
Highly Technical IBM Client
High technical understanding about
his domain, task oriented, 20+ years of
experience, in a senior role.
Learning Preference: Nitty-gritty for information
in his domain, high level information for
material he is unfamiliar with.
Mid-Highly Technical IBM Client
Mid-High technical understanding of her
domain, 10-19 years of experience, in a leadership role.
Learning preference: Quick answers to questions,
nitty-gritty only when needed.
Anyone in the IBM Universe* can find personalized search results based on user intent, profile, and history, every time they are looking for information at IBM.Anyone in the IBM Universe* can find personalized search results based on user intent, profile, and history, every time they are looking for information at IBM.
Anyone in the IBM Universe* can return to content they have already found without having to search.Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.
Anyone in the IBM Universe* can discover content through proactive delivery of resources, solutions, and guidance, without having to search.Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.
For seven weeks, 63 IBM Designers and 34 IBM Offering Managers from Germany, England, Ireland, Spain, China, Canada and all across the United States joined forces to collaborate in the immersive design studio in Austin, TX. During this experiential program, we honored our talents around the patterns of design, technology, and business to impact the people we serve.
Everyone wanted to feel heard—Everyone. Across. Twelve. Teams. These teams consisted of UX and visual designers, developers, researchers, and offering managers.I learned that I can only build trust and empathy with others by speaking up. I started thinking, “hmmm what would happen if I offered a different solution? Would they think less of me if I admitted I was wrong?” or “What if I told them that I felt disrespected?” Instead of wondering all of these thoughts, I verbalized them. I spoke up because this was a safe space to play.
We were given a project that focuses on fixing an issue that touches every part of IBM. It was an honor to be given a project to fix IBM search that will hopefully lead to a greater solution that will benefit the business in a positive way. As a UX designer this was a project that taught me a lot about the business and how UX can be implemented with the user in mind at all points of the design process. It felt great to be a part of such a high profile initiative.
It was not clear at the beginning of this project that we were focused on external facing clients only and that Google was tablestakes. As a team we felt like this was vital information that should have been shared earlier in the process, due to a lack of time. Saying that “everyone” is our user was too broad of a scope which led to some road blocks at the beginning. Also, it would have been very beneficial to learn more about the OM’s role because all of our OM’s were new to IBM so learning more about their expectations could have settled some conflicts that arose between design and OM.
