0 to 1 product feature, Cloud Connector, delivered within a two month contract
Timeline:
2 months
Team:
Product Manager, Front End Engineer, User Research
Role:
Snr Product Designer
“He worked diligently to iterate through ideas and his eagerness to test for clarity propelled his designs to a level that pushed the boundaries.”
Arlin Sorhaindo
Product Designer
“In my opinion, Stuart is a valuable asset to any team seeking an individual with his level of expertise and exceptional work ethic."
Marina Silva Tavares
Frontend Engineer
Summary
Problem
Customers want to direct traffic to public clouds, i.e. example.com/images to AWS S3. Because of security concerns, Cloudflare had to limit the generic way to do this to Enterprise customers. This leaves non-Enterprise customers having to use workarounds such as Workers. This decision has led to frustration within our community
Insight
Feedback was collected from Cloudflare community forum that all pointed towards the same problem. These qualitative insights were gather and validated by the Product Manager at the point when the project was being written up as a PRD.
Goal
Create a simple customer experience that tied into the existing feature set of the Cloudflare products. This was especially important for the R2 feature that could be promoted to customers and increase revenue for the business.
Deliverables
- User story definitions
- User flow diagrams
- High fidelity mock ups
- Prototype
- User testing
- Handover documentation
Definition
User stories were created to better understand and empathize with the customer on their journey
This type of exploration wasn’t part of the usual ways of working at Cloudflare. However I felt it was important, especially as someone new to the business, to better understand the path of the customer. I created a pack in Figma so that the team could continue to use this user story method after I left.
Created user flow diagrams to map out all the paths a customer could take with the new feature
Design
Wireframes were built to create a discussion point when talking with stakeholders about the features capabilities
With the user stories as my map, I created a series of wireframes covering the most important screens. Due to how highly interlinked the features of Cloudflare are, it quickly became clear that the hardest part of this project would be identifying all the edge cases and creating solutions to those micro problems.
Worked with the product manager to iterate and design the high fidelity Cloud Connector screens and experience
Identified and documented all validation errors in the Cloud Connector flows
The process of creating a Cloud Connection can be complicated at moments. It was important to ensure that customers were informed and instructed on how to rectify errors.
Utilized existing design system components to ensure v1 of the feature could be launched with minimal effort
Where necessary, created new components and added variants to existing components to support the new functionality
User testing
Coordinated with the research team to launch moderated usability tests with 4 Cloudflare customers
Worked with a researcher to agree on the questions that would be posed to candidates as they navigate through test. Due to the required technical knowledge to understand the use case of this new feature, it was decided to utilize the Cloudflare audience to test the usability of Cloud Connector.
Results
There was no complaints, concerns or issues with the usability of Cloud Connector. The only feedback that was received was whether our providers would be supported beyond the big 3, Azure, Google Cloud and AWS.
My time with Cloudflare finished before the feature was built and launched so no data is available on its success
If you would like to learn more from Cloudflare’s perspective on the feature, then you can read the article on their blog below.
Blog post
Get in contact
My inbox is always open to people looking to collaborate on interesting projects. Send a message to
stuartwalker559@gmail.com
Stuart Walker
Resume
Contact
0 to 1 product feature, Cloud Connector, delivered within a two month contract
Timeline:
2 months
Role:
Snr Product Designer
Team:
Product Manager, Front End Engineer, User Research
“He worked diligently to iterate through ideas and his eagerness to test for clarity propelled his designs to a level that pushed the boundaries.”
Arlin Sorhaindo
Product Designer
“In my opinion, Stuart is a valuable asset to any team seeking an individual with his level of expertise and exceptional work ethic."
Marina Silva Tavares
Frontend Engineer
Summary
Problem
Customers want to direct traffic to public clouds, i.e. example.com/images to AWS S3. Because of security concerns, Cloudflare had to limit the generic way to do this to Enterprise customers. This leaves non-Enterprise customers having to use workarounds such as Workers. This decision has led to frustration within our community
Insight
Feedback was collected from Cloudflare community forum that all pointed towards the same problem. These qualitative insights were gather and validated by the Product Manager at the point when the project was being written up as a PRD.
Goal
Create a simple customer experience that tied into the existing feature set of the Cloudflare products. This was especially important for the R2 feature that could be promoted to customers and increase revenue for the business.
Deliverables
- User story definitions
- User flow diagrams
- High fidelity mock ups
- Prototype
- User testing
- Handover documentation
Definition
User stories were created to better understand and empathize with the customer on their journey
This type of exploration wasn’t part of the usual ways of working at Cloudflare. However I felt it was important, especially as someone new to the business, to better understand the path of the customer. I created a pack in Figma so that the team could continue to use this user story method after I left.
Created user flow diagrams to map out all the paths a customer could take with the new feature
Design
Wireframes were built to create a discussion point when talking with stakeholders about the features capabilities
With the user stories as my map, I created a series of wireframes covering the most important screens. Due to how highly interlinked the features of Cloudflare are, it quickly became clear that the hardest part of this project would be identifying all the edge cases and creating solutions to those micro problems.
Worked with the product manager to iterate and design the high fidelity Cloud Connector screens and experience
Identified and documented all validation errors in the Cloud Connector flows
The process of creating a Cloud Connection can be complicated at moments. It was important to ensure that customers were informed and instructed on how to rectify errors.
Utilized existing design system components to ensure v1 of the feature could be launched with minimal effort
Where necessary, created new components and added variants to existing components to support the new functionality
User testing
Coordinated with the research team to launch moderated usability tests with 4 Cloudflare customers
Worked with a researcher to agree on the questions that would be posed to candidates as they navigate through test. Due to the required technical knowledge to understand the use case of this new feature, it was decided to utilize the Cloudflare audience to test the usability of Cloud Connector.
Results
There was no complaints, concerns or issues with the usability of Cloud Connector. The only feedback that was received was whether our providers would be supported beyond the big 3, Azure, Google Cloud and AWS.
My time with Cloudflare finished before the feature was built and launched so no data is available on its success
If you would like to learn more from Cloudflare’s perspective on the feature, then you can read the article on their blog below.
Blog post
Get in contact
My inbox is always open to people looking to collaborate on interesting projects. Send a message to stuartwalker559@gmail.com
Stuart Walker
Resume
Contact
0 to 1 product feature, Cloud Connector, delivered within a two month contract
Timeline:
2 months
Role:
Snr Product Designer
Team:
Product Manager, Front End Engineer, User Research
“He worked diligently to iterate through ideas and his eagerness to test for clarity propelled his designs to a level that pushed the boundaries.”
Arlin Sorhaindo
Product Designer
“In my opinion, Stuart is a valuable asset to any team seeking an individual with his level of expertise and exceptional work ethic."
Marina Silva Tavares
Frontend Engineer
Summary
Problem
Customers want to direct traffic to public clouds, i.e. example.com/images to AWS S3. Because of security concerns, Cloudflare had to limit the generic way to do this to Enterprise customers. This leaves non-Enterprise customers having to use workarounds such as Workers. This decision has led to frustration within our community
Insight
Feedback was collected from Cloudflare community forum that all pointed towards the same problem. These qualitative insights were gather and validated by the Product Manager at the point when the project was being written up as a PRD.
Goal
Create a simple customer experience that tied into the existing feature set of the Cloudflare products. This was especially important for the R2 feature that could be promoted to customers and increase revenue for the business.
Deliverables
- User story definitions
- User flow diagrams
- High fidelity mock ups
- Prototype
- User testing
- Handover documentation
Definition
User stories were created to better understand and empathize with the customer on their journey
This type of exploration wasn’t part of the usual ways of working at Cloudflare. However I felt it was important, especially as someone new to the business, to better understand the path of the customer. I created a pack in Figma so that the team could continue to use this user story method after I left.
Created user flow diagrams to map out all the paths a customer could take with the new feature
Design
Wireframes were built to create a discussion point when talking with stakeholders about the features capabilities
With the user stories as my map, I created a series of wireframes covering the most important screens. Due to how highly interlinked the features of Cloudflare are, it quickly became clear that the hardest part of this project would be identifying all the edge cases and creating solutions to those micro problems.
Worked with the product manager to iterate and design the high fidelity Cloud Connector screens and experience
Identified and documented all validation errors in the Cloud Connector flows
The process of creating a Cloud Connection can be complicated at moments. It was important to ensure that customers were informed and instructed on how to rectify errors.
Utilized existing design system components to ensure v1 of the feature could be launched with minimal effort
Where necessary, created new components and added variants to existing components to support the new functionality
User testing
Coordinated with the research team to launch moderated usability tests with 4 Cloudflare customers
Worked with a researcher to agree on the questions that would be posed to candidates as they navigate through test. Due to the required technical knowledge to understand the use case of this new feature, it was decided to utilize the Cloudflare audience to test the usability of Cloud Connector.
Results
There was no complaints, concerns or issues with the usability of Cloud Connector. The only feedback that was received was whether our providers would be supported beyond the big 3, Azure, Google Cloud and AWS.
My time with Cloudflare finished before the feature was built and launched so no data is available on its success
If you would like to learn more from Cloudflare’s perspective on the feature, then you can read the article on their blog below.
Blog post
Get in contact
My inbox is always open to people looking to collaborate on interesting projects. Send a message to stuartwalker559@gmail.com