01.
Persona polishing
We the core product team, went through many rounds of defining the primary persona. Settling on Lead DevOps. I was pleasantly surprised by the forthcoming nature of majority of our interviewed candidates.
TRACE / BITRISE
CI/CD PLATFORM BUILT FOR MOBILE DEVOPS
April 2020 - December 2021
B2C/B2B
HUNGARIAN OWNERSHIP
Bit breakdown
1
Bitrise an established mobile building platform (startup), well known in the mobile app world, acquired "Trace" a London start up for its expertise in mobile app development, specifically around crash log detection and reporting.
2
Building mobile software is an on going saga of version maintenance and deprecation. Therefor the endeavour of finding/fixing bugs needs to be easy, quick and cost effective.
3
Mobile apps generally crash from an accumulation of slight quirks rather than single large obvious event “generally". Studying historical event patterns can be fed into formulas for future event mishap detections.
4
Mobile app crashes can derive from poorly assembled or compiled builds, outside of the apps source code. Keeping a broad field of view on possible targets soon becomes challenging.
10 Backend Engineers
1 Front End/Full stack engineer
Developers code bases:
React
Java
Xcode
4 Product Designers
Softwares I used:
Figma & Figjam
Axure
Story Book
Jira
Bit breakdown
1
Bitrise an established mobile building platform (startup), well known in the mobile app world, acquired "Trace" a London start up for its expertise in mobile app development, specifically around crash log detection and reporting.
2
Building mobile software is an on going saga of version maintenance and deprecation. Therefor the endeavour of finding/fixing bugs needs to be easy, quick and cost effective.
3
Mobile apps generally crash from an accumulation of slight quirks rather than single large obvious event “generally". Studying historical event patterns can be fed into formulas for future event mishap detections.
4
Mobile app crashes can derive from poorly assembled or compiled builds, outside of the apps source code. Keeping a broad field of view on possible targets soon becomes challenging.
Developers
code bases:
10 Backend Engineers
1 Front End/Full stack engineer
React
Java
Xcode
Softwares
I used:
4 Product
Designers
Figma & Figjam
Axure
Story Book
Jira
Bit breakdown
1
Bitrise an established mobile building platform (startup), well known in the mobile app world, acquired "Trace" a London start up for its expertise in mobile app development, specifically around crash log detection and reporting.
2
Building mobile software is an on going saga of version maintenance and deprecation. Therefor the endeavour of finding/fixing bugs needs to be easy, quick and cost effective.
3
Mobile apps generally crash from an accumulation of slight quirks rather than single large obvious event “generally". Studying historical event patterns can be fed into formulas for future event mishap detections.
4
Mobile app crashes can derive from poorly assembled or compiled builds, outside of the apps source code. Keeping a broad field of view on possible targets soon becomes challenging.
10 Backend Engineers
1 Front End/Full stack engineer
Developers code bases:
React
Java
Xcode
4 Product Designers
Softwares I used:
Figma & Figjam
Axure
Story Book
Jira
PERSONA - LEAD DEVELOPER
"Catch bugs
before users do."
Omar's team are pragmatic, so often build functionality into their app in order to track performance where there are gaps in the monitoring, this is not ideal nor intended to be permanent.
Omar's challengers
Mobile app development focused on building stable apps for a "wide" set of devices, is exponential work.
Works in a small team of 7 people, they are all experienced at delivering mobile apps. Since they are a such a small team they don't have many eyes/ears on duty (on call).
Needs to ensure they are delivering a stable application, whist continuing to deliver features.
He needs to releases a new version of the app every 2 weeks.
PERSONA - LEAD DEVELOPER
"Catch bugs
before users do."
Omar's team are pragmatic, so often build functionality into their app in order to track performance where there are gaps in the monitoring, this is not ideal nor intended to be permanent.
Omar's challengers
Mobile app development focused on building stable apps for a "wide" set of devices, is exponential work.
Works in a small team of 7 people, they are all experienced at delivering mobile apps. Since they are a such a small team they don't have many eyes/ears on duty (on call).
Needs to ensure they are delivering a stable application, whist continuing to deliver features.
He needs to releases a new version of the app every 2 weeks.
PERSONA - LEAD DEVELOPER
"Catch bugs
before users do."
Omar's team are pragmatic, so often build functionality into their app in order to track performance where there are gaps in the monitoring, this is not ideal nor intended to be permanent.
Omar's challengers
Mobile app development focused on building stable apps for a "wide" set of devices, is exponential work.
Works in a small team of 7 people, they are all experienced at delivering mobile apps. Since they are a such a small team they don't have many eyes/ears on duty (on call).
Needs to ensure they are delivering a stable application, whist continuing to deliver features.
He needs to releases a new version of the app every 2 weeks.
Top 3
pain point themes
Following a series customer interviews run by our squad's dedicated researcher. We began to formulate a broader picture of what/where pains were being felt by potential customers. Here are 3 examples of these themes.
1 - All the data but no focus.
The team had done a good job at gathering data, the catch was that it didn't give any leading insight into what had lead up to the incident. Crashes most noticeably only showed up post the incident so you had to go back in time trying to establish the chain of incursions.
2 - Exponential probabilities.
3 - The tech stack of data calls & relays.
Top 3
pain point themes
Following a series customer interviews run by our squad's dedicated researcher. We began to formulate a broader picture of what/where pains were being felt by potential customers. Here are 3 examples of these themes.
1 - All the data but no focus.
The team had done a good job at gathering data, the catch was that it didn't give any leading insight into what had lead up to the incident. Crashes most noticeably only showed up post the incident so you had to go back in time trying to establish the chain of incursions.
2 - Exponential probabilities.
3 - The tech stack of data calls & relays.
Top 3
pain point themes
Following a series customer interviews run by our squad's dedicated researcher. We began to formulate a broader picture of what/where pains were being felt by potential customers. Here are 3 examples of these themes.
1 - All the data but no focus.
The team had done a good job at gathering data, the catch was that it didn't give any leading insight into what had lead up to the incident. Crashes most noticeably only showed up post the incident so you had to go back in time trying to establish the chain of incursions.
2 - Exponential probabilities.
3 - The tech stack of data calls & relays.
PARTS I PLAYED IN
PARTS I PLAYED IN
PARTS I PLAYED IN
SOME OF THE PROCESS
SOME OF THE PROCESS
My most noticeable positive impact:
1: Optimised Software Development Kit "SDK" registration process by 2/6 hours of onboarding time.
2: Increased user re-engagement by 40% with the Crash events journey display of millisecond time series log data.
01.
Persona polishing
We the core product team, went through many rounds of defining the primary persona. Settling on Lead DevOps. I was pleasantly surprised by the forthcoming nature of majority of our interviewed candidates.
01.
Persona polishing
We the core product team, went through many rounds of defining the primary persona. Settling on Lead DevOps. I was pleasantly surprised by the forthcoming nature of majority of our interviewed candidates.
02.
Workshop Wonders
I helped facilitate many a team workshop were we ran through users optimal registration flows, when loading their mobile app onto the Trace environment/app.
02.
Workshop Wonders
I helped facilitate many a team workshop were we ran through users optimal registration flows, when loading their mobile app onto the Trace environment/app.
02.
Workshop Wonders
I helped facilitate many a team workshop were we ran through users optimal registration flows, when loading their mobile app onto the Trace environment/app.
03.
Epic breakdowns
I often joined dev refinement sessions, to both get a clearer understanding of a domain, or for the discovery of the next product objective that may need my attention.
03.
Epic breakdowns
I often joined dev refinement sessions, to both get a clearer understanding of a domain, or for the discovery of the next product objective that may need my attention.
03.
Epic breakdowns
I often joined dev refinement sessions, to both get a clearer understanding of a domain, or for the discovery of the next product objective that may need my attention.
04.
Use case simulation
Soon after we concluded the bounds of an epic and the mix/stack of sub-tasks. I favoured running “How Might We” ideation sessions whilst the topics were fresh in the team’s mind. The goal was to draft a rich pool of concepts, that could be realised in clickable design prototypes.
04.
Use case simulation
Soon after we concluded the bounds of an epic and the mix/stack of sub-tasks. I favoured running “How Might We” ideation sessions whilst the topics were fresh in the team’s mind. The goal was to draft a rich pool of concepts, that could be realised in clickable design prototypes.
04.
Use case simulation
Soon after we concluded the bounds of an epic and the mix/stack of sub-tasks. I favoured running “How Might We” ideation sessions whilst the topics were fresh in the team’s mind. The goal was to draft a rich pool of concepts, that could be realised in clickable design prototypes.
05.
Design language
Shifting from the predominate over/use of the brand colour "purple" + having studied our researchers findings. Concluded a "sage green" could introduce a calming / mild celebratory sentiment. Massive thanks to heavy weight Harry Hogg our Lead Fronted engineer for his appreciation of design details.
05.
Design language
Shifting from the predominate over/use of the brand colour "purple" + having studied our researchers findings. Concluded a "sage green" could introduce a calming / mild celebratory sentiment. Massive thanks to heavy weight Harry Hogg our Lead Fronted engineer for his appreciation of design details.
05.
Design language
Shifting from the predominate over/use of the brand colour "purple" + having studied our researchers findings. Concluded a "sage green" could introduce a calming / mild celebratory sentiment. Massive thanks to heavy weight Harry Hogg our Lead Fronted engineer for his appreciation of design details.
06.
Component crafting
So as not to rock the design team too much, I went about incrementally introducing new evolutions of some out dated UI components. Here is simple docking of cards CTA to the bottom for better system VS insight data distinction.
06.
Component crafting
So as not to rock the design team too much, I went about incrementally introducing new evolutions of some out dated UI components. Here is simple docking of cards CTA to the bottom for better system VS insight data distinction.
06.
Component crafting
So as not to rock the design team too much, I went about incrementally introducing new evolutions of some out dated UI components. Here is simple docking of cards CTA to the bottom for better system VS insight data distinction.
07.
Concept, sketches
I was fortunate to have worked with such receptive team when it came to hack sessions. We had add hock sessions running anything from 10mins - 2hrs. Here we nailed the overview page wireframes over 2 x 1hr workshop sessions.
07.
Concept, sketches
I was fortunate to have worked with such receptive team when it came to hack sessions. We had add hock sessions running anything from 10mins - 2hrs. Here we nailed the overview page wireframes over 2 x 1hr workshop sessions.
07.
Concept, sketches
I was fortunate to have worked with such receptive team when it came to hack sessions. We had add hock sessions running anything from 10mins - 2hrs. Here we nailed the overview page wireframes over 2 x 1hr workshop sessions.
08.
Overview page is realised
Consolidated data through a new focused lens giving Omar a generalised sense of his App’s state, highlighting Health, Live Users, Active Users, New Users, User Events “Crash Free Sessions was a positive way to spin the data” Network Latency Version Adoption. Under Daily Weekly Monthly filter. Cheers to our Lead Engineer Harry for his craft.
08.
Overview page is realised
Consolidated data through a new focused lens giving Omar a generalised sense of his App’s state, highlighting Health, Live Users, Active Users, New Users, User Events “Crash Free Sessions was a positive way to spin the data” Network Latency Version Adoption. Under Daily Weekly Monthly filter. Cheers to our Lead Engineer Harry for his craft.
08.
Overview page is realised
Consolidated data through a new focused lens giving Omar a generalised sense of his App’s state, highlighting Health, Live Users, Active Users, New Users, User Events “Crash Free Sessions was a positive way to spin the data” Network Latency Version Adoption. Under Daily Weekly Monthly filter. Cheers to our Lead Engineer Harry for his craft.
09.
Weekly sync ups
Trace / Bitrise had quite a social aspect to it regardless of the dispersed remote nature of our team. Our dedicated squad researcher would often give us her findings, and more often than not lead to other conversations.
09.
Weekly sync ups
Trace / Bitrise had quite a social aspect to it regardless of the dispersed remote nature of our team. Our dedicated squad researcher would often give us her findings, and more often than not lead to other conversations.
09.
Weekly sync ups
Trace / Bitrise had quite a social aspect to it regardless of the dispersed remote nature of our team. Our dedicated squad researcher would often give us her findings, and more often than not lead to other conversations.
My most noticeable positive impact:
1: Optimised Software Development Kit "SDK" registration process by 2/6 hours of onboarding time.
2: Increased user re-engagement by 20% with the Crash events journey display of millisecond time series log data.
CRASHES SCREEN
< SLIDE >
EXAMPLES OF MY POSITIVE IMPACT ON
EXAMPLES OF MY POSITIVE IMPACT ON
CRASHES SCREEN
< SLIDE >
BEFORE
Blind list of high level stats
Sure it was handy to have a list of all the counted Crashes, App versions and Users, but they failed to give any insight into what/where/how events contributed to the crashes that took place.
AFTER
Spot a crash in a flash
Omar's crashes are indicated with Red flags in the micro events timeline. Interactions shown in 24 hrs of events. The User journey stack of events, call out problem "blocks" for inquiry. Wouldn't have been possible without Harry's full stack of skills and design appreciation.
Richer insights of crashes build up
CPU and Memory Usage are in sync with the User Journey stack of events. This gives a far more detailed picture of what could have contributed to a crash. Then Omar would know were and when to look in their log files to drill into the culprit.
PERFORMANCE SCREEN
PERFORMANCE
SCREEN
< SLIDE >
PERFORMANCE SCREEN
< SLIDE >
BEFORE
Data with little insight becomes hard work
Data with little insight is hard work
The data doesn't have any indication of were to look or for what reason.
You don't any sense if a metric is under or over performing.
AFTER
Pushing data upstream
Rolled up data trend values now informs Omar through a focused lens.
Wouldn't have been possible without Harry's full stack of skills and design appreciation.
By calling out the performance trend of a metric, in a natural language statements "Crash free sessions(98%) is 9% lower compared to 7days prior" help normalised the sense of trust between the data. Over time this trust could be expanded to present new Benchmarks or Strategies.
Why? Trace / Bitrise was focusing on pushing Benchmarking as a go to market USP.
Rolled up data trend values now informs Omar's through a focused lens.
By calling out the performance trend of a metric, in a natural language statements "Crash free sessions(98%) is 9% lower compared to 7days prior" help normalised the sense of trust between the data. Over time this trust could be expanded to present new Benchmarks or Strategies.
Why? Trace / Bitrise was focusing on pushing Benchmarking as a go to market USP.
BEFORE
The data doesn't have any indication of were to look or for what reason.
You don't any sense if a metric is under or over performing.
Data with little insight becomes hard work
AFTER
Pushing data upstream
Rolled up data trend values now informs Omar through a focused lens.
Wouldn't have been possible without Harry's full stack of skills and design appreciation.
By calling out the performance trend of a metric, in a natural language statements "Crash free sessions(98%) is 9% lower compared to 7days prior" help normalised the sense of trust between the data. Over time this trust could be expanded to present new Benchmarks or Strategies.
Why? Trace / Bitrise was focusing on pushing Benchmarking as a go to market USP.
CRASHES SCREEN
< SLIDE >
BEFORE
Blind list of high level stats
Sure it was handy to have a list of all the counted Crashes, App versions and Users, but they failed to give any insight into what/where/how events contributed to the crashes that took place.
Spot a crash in a flash
AFTER
Omar's crashes are indicated with Red flags in the micro events timeline. Interactions shown in 24 hrs of events. The User journey stack of events, call out problem "blocks" for inquiry. Wouldn't have been possible without Harry's full stack of skills and design appreciation.
Richer insights of crashes build up
CPU and Memory Usage are in sync with the User Journey stack of events. This gives a far more detailed picture of what could have contributed to a crash. Then Omar would know were and when to look in their log files to drill into the culprit.
EXAMPLES OF MY
POSITIVE IMPACT ON
TRACE / BITRISE
CI/CD PLATFORM BUILT FOR MOBILE DEVOPS
B2B
HUNGARIAN OWNERSHIP
April 2020 - December 2021
TRACE / BITRISE
CI/CD PLATFORM
BUILT FOR
MOBILE DEVOPS
B2C/B2B
HUNGARIAN OWNERSHIP
April 2020 - December 2021
bit
bit
by
by
bit
bit