Select Page

Hello, I’m Mark.

A UX designer for complicated projects.

Thanks for taking a look!

For some background, my Bachelor and Masters degrees are in Computer science in the specialty area of HCI.

A mixture of computers, art, and psychology.

Most recently, I have worked with Google as the researcher and designer on the TensorFlow app. I came in as the first UX person for what used to be a research project. I worked with the developers to improve their process of creating ML models, at the same time showing what UX can do for them. 


I managed all UX research within Azure for 4 development teams simultaneously. 


The startup Vidible was bought by Aol, which was then bought by Verizon. I was the single UX researcher adapting to constant change in priorities.


I designed the internal tools and metrics to make tools easier for the internal employees; to get their job done faster and with higher satisfaction.

Hamlyn Institute

Development of research ideas on how to improve the UI for the robotic surgery. Trying to make sure the surgeon doesn’t get lost when driving the robot in the abdominal cavity.


Development of UI for mobile apps “next billion” users and accessibility research

Process example

Since the team I was working with had not worked with UX before, the goal I was given was to “fix the UX”.

After some stakeholder interviews I came up with speeding up the model creation process, and making it easier for developers to make faster ML models.

To start, I set out to find the problems for developers. I started with interviews & surveys (internally) and interviews & survey posters at conferences (image at right) looking for choke points.  I was able to map out the different persona groups, the steps different developer groups are taking, the time they spent at each step, and what they saw as time wasted.

Once I was able to prioritize the problems affecting the most people, causing the biggest slowdowns, and the biggest headaches; the biggest problem was how difficult it was to debug ML models.

I switched modes to sprint development so I could quickly iterate between working with developers to figure out what is possible for the design, then user testing those designs to find problems, and then surveys to find out the size of the problems to fix in the next design.  

After going through a few iterations, it is currently being built and the starting version can be found found at the TensorBoard Debugger.

More design examples can be supplied by request.

You can also view my  Github interaction with the TensorBoard and Cirq teams.

If you are interested in more info about me, you are free to listen to the podcast I host or read articles I have written.

Feel free to reach out with any questions and thank you again for taking a look.

The extra UX headaches for AI in production

The extra UX headaches for AI in production

It used to be that UX would work with the developers to create a good experience. Dev would build it and then QA would verify it. After that the product would be released and the team moved on to new features. This still works for non-AI products.The current process...

3 steps to ensure AI doesn’t make your product worse

3 steps to ensure AI doesn’t make your product worse

As AI becomes better it has started to become a differentiator between products being offered by different companies there is a push to put it into everything. The idea is so pervasive it lead to a whole genre of memes on using AI as the solution to anything. So where...

AI specific issues while user testing

AI specific issues while user testing

Machine learning is one of the strategies many companies are using as they try to improve and differentiate their product by augmenting the user’s experience. Building artificial intelligence into apps can improve what can be done for customers and users, but can also...