As a Quality Analyst (QA) in the office, being the person looking for errors could cause a hostile relationship with developers.
Good pull request feedback is important but can be tricky to get on busy projects. Here are a few tips to get better feedback.
Giving feedback can be uncomfortable, and the way we deliver it can have a huge impact. Let's look at how to give good feedback.
Any form of feedback requires trust to succeed. The 5-15 process only works if you actually address the employee feedback.
If you can find a space for every voice at the table during design feedback, you might be surprised by the richness of the conversation.
Is your client asking for feedback on their team? Part 2: Let's set some goals to make the conversation productive and positive.
Is your client asking for feedback on their team? With some context and preparation, these conversations can be productive and positive.
I recently wrote about making the most of a software beta trial. Next, I’ll talk about what to do after the beta is over and the data is in.
Want real, constructive feedback on your work? Try ruthless critique – an extremely thoughtful, very direct, and sometimes contentious review.
How to leverage the three components of a PID loop to address problems and improve your relationship with clients (and everybody else).
An intro to the PID control algorithm, with a breakdown of its three components (Proportional, Integral, and Derivative) and their different purposes.
Design critiques are a great way to hone your skills and improve your projects. Here's what I've learned about giving and receiving productive critique.