In today’s tech landscape, users are increasingly demanding for a platform that is accessible, reliable, efficient, useful, and delightful. We'll develop a go-to-market plan that accelerates us beyond the competition.

User Engagement

A product is only useful if people use it, so engaging users early in the process is necessary. Interview target customers on their wants and needs to align our initiatives on what we should build.

Competitive Analysis

Researching competitive products provides inspiration and can give a competitive advantage on creating a solution that stands out.

Ideation

Based on informed data and collaboration, we create a whole list of potential solutions. My personal favorite way of orchestrating this is using the Design Sprint Methodology.

My Preferred Strategy Tools: Notion & Lucidchart

I’m obsessed with having blank canvases and spaciousness. Creating a poster full of data laid out in front of you not only allows you to see the data, but begin drawing relationships to what’s working / not working. It offloads your logical mind so that you can harness your creativeness throughout every step of the way.

The freedom to express ideas with data excites me every day.

I take mathematical approach to wire framing, display prototypes through user stories, and layout my CSS to be flexible. Depending on the users and the nature of the foundation, designing using the latest technology is preferred.

Prototyping

After identifying a solution, I'll create a prototype to obtain early feedback from users, and go through multiple iterations until I land on the right design. I personally love to use Sketch and have more recently explored Framer.

User Testing

Prototypes are shown to real users and recording feedback as it comes in, which then get used in its iterations to form a final design. I pay close attention to emotional responses and comprehension.

Minimal Viable Product

Keep it stupid simple! At this stage I'll scope the project down and aim to deliver an experience that's useful to our users. This helps minimize unnecessary features, reduce risks, and speed time to market.

My Preferred Design Tool: Figma & Slides

Telling stories is one of the most powerful means that leaders have to influence, teach, and inspire — something I love to do through design. I think the best stories enable users to connect, learn, share, and create.

And like people, products also get to engage with others in the same way.

Code gets to be as modular and extendable as possible to reduce future tech debt. I prefer a modular design pattern and utilizing web components if available.

Agile and Test-Driven Development

This insures a high quality product gets pushed into production.

Scalable and Fault-tolerant

I believe having a beautiful design isn't complete without beautifully written code. I like to ensure we're using modular and reusable web components to drive faster development, and increase test coverage to reduce risks.

My Preferred Develop Tool: Visual Code

It’s easy for code to get messy. Having to use best code design patterns up front and staying organized allows for faster expansion. Developers get to understand elegant code so they can further develop upon a foundation, especially upon projects with deadlines.

Creating APIs opens up communication between users, machines, and the mix. Even with code, the experience gets to be accessible, reliable, efficient, useful, and delightful.

4. Assess

Ensure we measure product functionality and customer perception that will evaluate our success and fuel data to other projects.

Measure Success

Adding tracking around feature set will support in examining the success of the feature, along with giving us indicators on whether a product feature is functioning properly.

My Preferred Validation Tool: Tealium, MixPanel, and Optimizely

Not every golden solution is perfect the first time. Feedback is our key to learn, grow, and become better overtime. It may also bring rewarding closure to any project.