A UX Questionnaire with Vince Heilman
Explain a typical day for you.
Here's a recap of 5 UX questions that I was recently asked during an interview.
Explain a typical day for you.
What are your biggest UX challenges?
Explain a typical day for you.
Explain a typical day for you.
A typical Monday will start with meeting my team for a standup to discuss our priorities and deliverables for the week, then meet again in the middle of the week to check progress when necessary. A typical day will have time blocks allotted for design and documentation of current projects, as well as smaller team meetings to create user stories, review wireframes, requirements, and to troubleshoot any issues. Once a week, I also attend a weekly meeting where I present my department’s progress to members of the executive board. On Fridays, I’d get written updates from the team of all tasks completed and upcoming. Finally, I’d create a list of priorities for next week, and send off the weekly summary to my superior.
What are your biggest UX challenges?
Buy-in and Ego. Buy-in from Executive Team, Product Owners, Developers, and Users sounds easy, but everyone needs to be on the same page. Early planning and user-testing of designs can create huge savings in time and cost of development projects. Ego can create problems sometimes, when team members will have special requests that aren’t in-line with user needs or objectives. I’ve had developers, under deadlines, resist design patterns because it’s not in their library and custom code is needed. This is a valid discussion to have with stakeholders, and sometimes new patterns need to be test with users.
Explain a typical day for you.
A typical Monday will start with meeting my team for a standup to discuss our priorities and deliverables for the week, then meet again in the middle of the week to check progress when necessary. A typical day will have time blocks allotted for design and documentation of current projects, as well as smaller team meetings to create user stories, review wireframes, requirements, and to troubleshoot any issues. Once a week, I also attend a weekly meeting where I present my department’s progress to members of the executive board. On Fridays, I’d get written updates from the team of all tasks completed and upcoming. Finally, I’d create a list of priorities for next week, and send off the weekly summary to my superior.
Explain a typical day for you.
A typical Monday will start with meeting my team for a standup to discuss our priorities and deliverables for the week, then meet again in the middle of the week to check progress when necessary. A typical day will have time blocks allotted for design and documentation of current projects, as well as smaller team meetings to create user stories, review wireframes, requirements, and to troubleshoot any issues. Once a week, I also attend a weekly meeting where I present my department’s progress to members of the executive board. On Fridays, I’d get written updates from the team of all tasks completed and upcoming. Finally, I’d create a list of priorities for next week, and send off the weekly summary to my superior.
Explain a typical day for you.
A typical Monday will start with meeting my team for a standup to discuss our priorities and deliverables for the week, then meet again in the middle of the week to check progress when necessary. A typical day will have time blocks allotted for design and documentation of current projects, as well as smaller team meetings to create user stories, review wireframes, requirements, and to troubleshoot any issues. Once a week, I also attend a weekly meeting where I present my department’s progress to members of the executive board. On Fridays, I’d get written updates from the team of all tasks completed and upcoming. Finally, I’d create a list of priorities for next week, and send off the weekly summary to my superior.
