#design feedback

When you seek feedback from a junior designer about your current design, unexpected outcomes may arise.

Things can go unexpectedly.

Some people are very honest, and their feedback can be uncomfortable and invaluable in helping organizations achieve their goals at the same time.

Also, I learned this in my first job to give attention to the suggestions of young minds.

More importantly, if they are 4-5 years younger or more, then definitely you should urge them as a senior to share their thoughts.

Because when the ego takes a step back and lets creative ideas take the lead, the businesses are expected to perform in ways that can be unimaginable.

Credits: I quit my job and followed my passion… | Gabblin (YouTube) Gabblin Logo | Gabblin Motion Pictures (LinkedIn)

Disclaimer: All rights to the original creator. Shared under fair use for meme/commentary purposes.

Importance of product management in today's business landscape?

Product management is a critical function in any organization that produces software products or services. It involves overseeing the entire product lifecycle, from ideation and research to development, launch, and ongoing updates and improvements. In today's business landscape, product management is more important than ever. With the rapid pace of technological change and intense competition in many industries, companies need to stay agile and responsive to customer needs in order to stay ahead. Effective product management helps businesses to: 1. Understand customer needs and preferences: Product managers conduct market research and gather feedback from customers to identify pain points and opportunities for improvement. 2. Prioritize development efforts: With limited resources, it's essential to focus on creating the features and functionality that will have the biggest impact on customers and the business. 3. Ensure quality and reliability: Product managers work closely with development teams to ensure that products are well-designed and free from bugs and glitches. 4. Keep up with the competition: By monitoring the market and staying aware of competitor offerings, product managers can identify emerging trends and quickly respond with new features and updates. Overall, effective product management enables companies to be more innovative, customer-centric, and successful in today's fast-paced business environment.

Here's a simple example of regression testing: Let's say you have a website that allows users to create accounts, log in, and make purchases. After several months of usage, you realize that the registration process is too long and confusing for users. You decide to make some changes to streamline the process. However, before implementing these changes, you want to make sure that they do not break any of the existing functionality of the website. To do this, you would perform regression testing. You would set up a test environment, where you would run the existing test scenarios to verify that the changes you made to the registration process do not affect the ability of users to log in or make purchases. You would also add new test cases to validate the changes to the registration process. Regression testing should be performed whenever there are changes made to the software application, such as bug fixes, new features, or enhancements to existing features. It ensures that the quality of the software remains high and that any changes made do not affect the existing functionality of the software. The process of regression testing typically involves the following steps: 1. Identify the test cases that will be affected by the changes. 2. Prepare the test environment by setting up the necessary hardware, software, and data. 3. Rerun the selected test cases on the modified code. 4. Compare the results of the previous test runs with the new test runs. 5. Analyze any failures or inconsistencies and investigate the root cause. 6. Update the test cases and test environment as needed. 7. Repeat the process until all the test cases pass and the quality of the software is validated.

Automated tools for sanity testing can be used for the following:

Script Writing: Create scripts that build tests, which provide clarity on how potential bugs will be dealt with and help with bug detection.

Script Executions: Execute scripts that are written with automated tools to quickly detect any potential issues or inconsistencies in the software or system being tested.

Regression Testing: Automatically check for changes in system behavior after a change occurs by running comparative tests before and after the change is made in order to detect any unexpected issues or regressions.

Report Generating: Generate reports that help identify which bugs were found and provide information about where those bugs originated from so they can be addressed properly and efficiently.

The use of automated tools makes it easier to monitor system performance and detect any bugs, allowing you to create an effective Quality Assurance process for your software products and applications.

When giving design feedback, don't solve the problem for the designer. Tell them the goal that's NOT being met, and let them figure out how to achieve it. This is a simple switch to make in how you give design feedback, but it makes a huge difference. Another way to think about it is: give designers goal-based feedback, not design-based feedback. For instance: • [Design-based] Can you change this button color to a darker blue? • [Goal-based] I feel like the site is too informal, and one of our goals is "Users should feel that we are professional and trustworthy" The first is the epitome of cringe-worthy design feedback (no, strike that – it would be "bigger logo" or "make it pop"). The second will MAKE THE DESIGNER LOVE YOU. You're letting them do their job (which is, for the record, translating a business goal into an interface). Another example: • [Design-based] Let's use a carousel to show multiple images here. • [Goal-based] There are 3 primary messages we want to communicate with this page, and right now, only one of them is coming through. Again, the first is awful. Not only does it prescribe the solution, but that "solution" happens to be "let's make users wait 10,000 milliseconds without scrolling or looking at anything else, in order to read 3 sentences that they can only navigate between by clicking tiny half-invisible dots." Carousels are a stain on digital interfaces. Seriously. One more: • [Design-based] Let's move this button to the right side of the screen and make it bigger. • [Goal-based] The primary goal of this page is to get people to sign up, and right now, very few people are clicking the signup button. When you give a designer feedback like "move this button", they ultimately have to figure out why you want them to move the button anyways. Better to just give the why in the first place and save you both a meeting next week.