Project Feedback

Systems without feedback break.

Feedback is the concept of sending information about an event back to the original source to improve the performance of the system.

Feedback is the fuel for learning and growth. Systems with continuous feedback (learning) can constantly experiment and fail, but eventually hone in on their goal (growth). Since feedback is critical to success, we need guiding principles and systems for giving and receiving feedback for people, projects, products, and processes.

Giving and receiving feedback for people is the most important type of feedback, so it deserves its own page: https://globalvisioninc.atlassian.net/wiki/pages/resumedraft.action?draftId=2632614230

Projects, products and processes

Projects, products, and processes need collaboration and feedback from many individuals and teams to leverage the diversity in thought and approach we all bring to the table.

Build-Build-Build is not sustainable and most of what you build will fail ❌

At GlobalVision, we follow a 4 step process:

Step 0. Document

Documentation-first means that for anything to change, the first thing we do is create a shareable document.

• If you save documentation for the end, it will never happen.

• Get early feedback from the target audience

Step 1. Build

Build the absolute smallest scope possible to minimize waste.

Step 2. Measure

Determine how to measure success for the change.

Step 3. Learn

Seek out feedback and measure the impact of the change.

Repeat.

Continue iterating through this cycle. Iteration of small changes will allow us to “fail-fast” and maintain agility.

How to get feedback

The easiest way is to ask! This is explained in Writing Principles | 6.-Open-for-feedback:

• Whenever starting something new, always save time to ask for feedback (eg. please send feedback before Thursday)

• Include instructions on how to give the feedback (eg. reply in the thread for any feedback)

For more consistent feedback: build feedback systems. Here are some examples:

• Schedule recurring with the team for projects and processes

• Send recurring surveys (eg. employee satisfaction survey)

• Create always-on feedback capturing systems (eg. product improvement engine)

This does not mean we work through consensus. The person who's responsible for the work ultimately decides, but they should always ask for feedback, take each suggestion seriously, and then explain why the decision was made using our .