My Framer Site

Engagement Overview

Microsoft and Insight teamed up to sponsor a hackathon for American Airlines at their headquarters located in Ft. Worth, Texas. This two-day event was intended to elevate Microsoft’s PowerApps’s usage in American Airline’s current operations.

Eight teams participated by producing solutions to known areas of opportunity. At the conclusion of the hackathon, three teams were selected (from a panel of American Airline leadership) to continue building out use cases in order to prove business value. This allotted time was short (6 weeks) but the potential outcomes were potentially lifesaving.

The Challenge

Microsoft and Insight teamed up to sponsor a hackathon for American Airlines at their headquarters located in Ft. Worth, Texas. This two-day event was intended to elevate Microsoft’s PowerApps’s usage in American Airline’s current operations.

Eight teams participated by producing solutions to known areas of opportunity. At the conclusion of the hackathon, three teams were selected (from a panel of American Airline leadership) to continue building out use cases in order to prove business value. This allotted time was short (6 weeks) but the potential outcomes were potentially lifesaving.

The Need

Microsoft and Insight teamed up to sponsor a hackathon for American Airlines at their headquarters located in Ft. Worth, Texas. This two-day event was intended to elevate Microsoft’s PowerApps’s usage in American Airline’s current operations.

Eight teams participated by producing solutions to known areas of opportunity. At the conclusion of the hackathon, three teams were selected (from a panel of American Airline leadership) to continue building out use cases in order to prove business value. This allotted time was short (6 weeks) but the potential outcomes were potentially lifesaving.

My Contribution

Introduction to user experience, what it is, and why it
is important
Several members across the mostly development and subject matter expert
comprised teams have never worked directly with representatives of User
Experience.

I introduced and sold the benefits of engaging with UX early in the life a product.

Built trust with a team through daily stand-ups, transparent conversation, and identification of roles and responsibilities.

This was all done remotely, with language barriers and two different time zones.
Facilitated remote “discovery session” to identify “statement starters” and to align on what problem we are trying to solve
With different disciplines, knowledge and expertise, this is important to ensure each team member contributes to these exercises, allowing various perspectives to a known problem.

The design thinking activities allowed participants identify not only possible solutions but technical limitations as well. (ex: How might we prevent passengers from leaving the terminal without their personal belongings?)
Helped identify measurements of success
Guided conversations to select Key Performance Indicators, Business Use Cases

With the help of subject matter experts on the team, we were able to narrow our focus to some simple metrics (adoption, time spent in legacy systems, and lives saved during jet bridge inspections)
Constructed team back logs with MVP in mind
As always, time was a constraint as the finish line was an executive review with a live product demo to be evaluated for their validity.

Coached and guided team to make decisions with MVP and original scope in mind, while capturing enhancements for subsequent product releases/updates.
Evaluated current work flows
Conducted moderated testing with users to uncover qualitative data which drives the design decision making process.

Mock ups to illustrate possible solutions
Introduction to user experience, what it is, and why it
is important
Several members across the mostly development and subject matter expert
comprised teams have never worked directly with representatives of User
Experience.

I introduced and sold the benefits of engaging with UX early in the life a product.

Built trust with a team through daily stand-ups, transparent conversation, and identification of roles and responsibilities.

This was all done remotely, with language barriers and two different time zones.
Facilitated remote “discovery session” to identify “statement starters” and to align on what problem we are trying to solve
With different disciplines, knowledge and expertise, this is important to ensure each team member contributes to these exercises, allowing various perspectives to a known problem.

The design thinking activities allowed participants identify not only possible solutions but technical limitations as well. (ex: How might we prevent passengers from leaving the terminal without their personal belongings?)
Helped identify measurements of success
Guided conversations to select Key Performance Indicators, Business Use Cases

With the help of subject matter experts on the team, we were able to narrow our focus to some simple metrics (adoption, time spent in legacy systems, and lives saved during jet bridge inspections)
Constructed team back logs with MVP in mind
As always, time was a constraint as the finish line was an executive review with a live product demo to be evaluated for their validity.

Coached and guided team to make decisions with MVP and original scope in mind, while capturing enhancements for subsequent product releases/updates.
Evaluated current work flows
Conducted moderated testing with users to uncover qualitative data which drives the design decision making process.

Mock ups to illustrate possible solutions
Introduction to user experience, what it is, and why it
is important
Several members across the mostly development and subject matter expert
comprised teams have never worked directly with representatives of User
Experience.

I introduced and sold the benefits of engaging with UX early in the life a product.

Built trust with a team through daily stand-ups, transparent conversation, and identification of roles and responsibilities.

This was all done remotely, with language barriers and two different time zones.
Facilitated remote “discovery session” to identify “statement starters” and to align on what problem we are trying to solve
With different disciplines, knowledge and expertise, this is important to ensure each team member contributes to these exercises, allowing various perspectives to a known problem.

The design thinking activities allowed participants identify not only possible solutions but technical limitations as well. (ex: How might we prevent passengers from leaving the terminal without their personal belongings?)
Helped identify measurements of success
Guided conversations to select Key Performance Indicators, Business Use Cases

With the help of subject matter experts on the team, we were able to narrow our focus to some simple metrics (adoption, time spent in legacy systems, and lives saved during jet bridge inspections)
Constructed team back logs with MVP in mind
As always, time was a constraint as the finish line was an executive review with a live product demo to be evaluated for their validity.

Coached and guided team to make decisions with MVP and original scope in mind, while capturing enhancements for subsequent product releases/updates.
Evaluated current work flows
Conducted moderated testing with users to uncover qualitative data which drives the design decision making process.

Mock ups to illustrate possible solutions
Introduction to user experience, what it is, and why it
is important
Several members across the mostly development and subject matter expert
comprised teams have never worked directly with representatives of User
Experience.

I introduced and sold the benefits of engaging with UX early in the life a product.

Built trust with a team through daily stand-ups, transparent conversation, and identification of roles and responsibilities.

This was all done remotely, with language barriers and two different time zones.
Facilitated remote “discovery session” to identify “statement starters” and to align on what problem we are trying to solve
With different disciplines, knowledge and expertise, this is important to ensure each team member contributes to these exercises, allowing various perspectives to a known problem.

The design thinking activities allowed participants identify not only possible solutions but technical limitations as well. (ex: How might we prevent passengers from leaving the terminal without their personal belongings?)
Helped identify measurements of success
Guided conversations to select Key Performance Indicators, Business Use Cases

With the help of subject matter experts on the team, we were able to narrow our focus to some simple metrics (adoption, time spent in legacy systems, and lives saved during jet bridge inspections)
Constructed team back logs with MVP in mind
As always, time was a constraint as the finish line was an executive review with a live product demo to be evaluated for their validity.

Coached and guided team to make decisions with MVP and original scope in mind, while capturing enhancements for subsequent product releases/updates.
Evaluated current work flows
Conducted moderated testing with users to uncover qualitative data which drives the design decision making process.

Mock ups to illustrate possible solutions

The Solution

NIKONOW