Signed in as:
filler@godaddy.com
ALIGN
Given that the original Raven platform was developed in ColdFusion, a complete rebuild was proposed to meet current security standards and provide a revamped user experience. The project kicked off by convening the steering committee to map out product objectives. Since Raven is utilized by both internal Teledyne FLIR employees and external contractors, representatives from Teledyne's marketing team were included in the steering committee.
The project team then categorized business objectives into short-term and long-term goals. The internal team then began to explore how to establish baselines and achieve the high-level objectives. Among our list of objectives were:
- Generate Marketing Content
- Enhance Web Application Security
- Create an Intuitive User Experience
- Reduce Time Internal Users Spend Surveillance Plans
EMPATHIZE & DEFINE
The core project team initiated the project by conducting a comprehensive analysis of Raven's current state. We collaborated closely with subject matter experts (SMEs) to gain a deep understanding of existing workflows and identify key user groups. With a clear grasp of Raven’s framework and user goals, I spearheaded ethnographic research, shadowing five internal Raven users as they navigated tasks within the original platform. Users were also asked to reference any external tools they utilized in completing designs within Raven, prompting additional shadowing of these external systems when identified.
The pain points observed during these shadowing sessions were systematically categorized using the Red Routes methodology, based on the number of users affected and the frequency of occurrence. In addition, Single Usability Metrics were gathered during each session. By focusing on the most commonly and frequently experienced pain points, we established baseline completion times for critical tasks, which served as key results under the objective of "Creating an Intuitive User Experience." We also benchmarked the overall time required for designing surveillance plans.
Understanding the processes of Teledyne FLIR sales representatives, who rely on these surveillance plans to calculate the total cost of cataloged items, was essential to uncovering opportunities within the objectives of "Reducing Time Internal Users Spend on Surveillance Plans" and "Generating Marketing Content." Through contextual inquiries with the sales team and an analysis of historical data, we established benchmarks for the time spent on tallying and sending quotes for surveillance plans, as well as insights into how they evaluate product lines for potential interest.
Building on the external tools identified, I conducted a thorough review of similar platforms, analyzing their strengths, weaknesses, and features. This competitive research informed the identification of industry best practices and innovative solutions that could be adapted to enhance Raven’s user experience.
IDEATE & TEST
Utilizing the insights gained from our initial research and analysis, we proceeded to the ideation phase.
Armed with a comprehensive understanding of both user pain points and competitor offerings, we facilitated brainstorming sessions with cross-functional teams. Ideas were evaluated based on their potential impact on user experience and alignment with our project objectives.
Following ideation, we entered the prototype testing phase. Low-fidelity prototypes were quickly developed to iterate on the most promising concepts. These prototypes were tested with internal Raven users, who were asked to complete tasks similar to those in the original platform. The testing process included metrics from our initial benchmarking as well as comparisons against competitor performance. User feedback and key performance indicators, such as task completion time and user satisfaction, were rigorously analyzed to assess the effectiveness of each prototype. By setting measurable targets for improvements in task completion times, user satisfaction, and competitive positioning, we ensured that our solutions not only met internal benchmarks but also provided a clear advantage in the market.
PLAN
Following the ideation and testing phase, we collaborated with our Product Owner to prioritize features using an Importance/Difficulty Matrix. This prioritization informed the development of a comprehensive implementation backlog, timeline, and project estimate, providing the client with a clear and structured plan for moving forward. The plan also included a track for continued discovery and benchmarking objectives.
After the implementation phase kicked off, we worked closely with the Senior Visual Designer to ensure that the modern user experience was complemented by a sleek, contemporary visual design. Together, we developed a cohesive design language that aligned with the overall user experience goals while reinforcing the brand’s identity. This design language was meticulously documented in the Design System.
Operating within an emergent design practice, we meticulously refined micro-interactions to enhance the overall user experience, ensuring that every visual detail contributed to a seamless and intuitive interface. Additionally, we provided the development team with detailed flow charts and wireflows to clearly illustrate interactions beyond the high-level flows identified in the discovery phase. These visual aids were crucial in guiding the development process and ensuring that the design intent was fully realized.
We also played a key role in shaping the acceptance criteria, working closely with both the development and quality assurance teams to ensure that interactions were properly built and tested. Our collaborative efforts culminated in a product that was visually appealing, functionally robust, and fully aligned with both the client’s and users’ expectations.
Raven 2.0 was publicly launched in October 2023, with all users of the previous system migrating ahead of the sunsetting of Raven 1.0 on January 1st, 2024. Since the launch, the team has prioritized the scope for the next phase of the project.
