Ryan Wilson talking about doing the right thing, working both hard and smart, asynchronous communication and console logs in bug reports.
Bitovi has built apps and done UX work with Apple, Nokia, Levi's, Lowe's, Sam's Club, CALI, and HaulHound to name a few.
Creating a great product comes down to great communication between the team, the stakeholder, and the users while the product is being built. However, I would say that it doesn't hurt to have your product built by a team with extensive knowledge in what they do.
What makes a great team is trust. Trust in the ability to represent the company to people outside the company. Trust in "doing the right thing" both based on requirements as well as best practices.
Written and verbal communication is a necessity whether you are remote or not. Bitovi has been a fully remote company since we started in 2006 – we rely on asynchronous communication – style guides, commenting on issues, great documentation, etc. – as well as great synchronous communication like to how you present yourself on camera in standup.
Two things that I would like to pass along:
'Work Smarter Not Harder' – Working both smart and hard are essential for great outcomes.
If I would have been born 50 years earlier I probably would have been a Sociologist or worked in Marketing. Both have principles that greatly overlap with being a User Experience Designer.
All of my apps are meticulously organized on my Home Screen... but the ones I could not do without are Notion (for notes, documentation, and internal project tracking), Slack (for all company and client communications), and Spark (so that I can always stay up on my emails and calendar events).
GitHub - I like how simple GitHub is in relation to Jira.
I choose 'many things that do one thing really well'. IMO the more an app tries to do the worse the user experience ... cough cough MS Teams ;)
I'm a "deploy to prod only after you've built it in dev and tested it in qa" sort of person.
I'm all about "fail fast and fail often" when developing the concept of the application and getting user feedback to iterate to the next round. However, when things don't work correctly in production it greatly affects how users perceive your product.
What makes some bug reporting better than others is the level of detail included in the report. Bug reporting without screenshots, a method of reproduction, or console details is relatively worthless.
If I magically had more time on a project I would use that time to do more user testing for new features, or adding more detail to the style guide or documentation.
Get visual proof, steps to reproduce and technical logs with one click
Continue reading
Try Bird on your next bug - you’ll love it
“Game changer”
Julie, Head of QA
Try Bird later, from your desktop