Skip to content
This repository was archived by the owner on Oct 15, 2021. It is now read-only.
This repository was archived by the owner on Oct 15, 2021. It is now read-only.

Close the loop and ask for user feedback #22

Description

@dontpanicgr

One can notice that although we work in Agile product development cycle there is one phase of the process that we partially (or not) have done effectively and it is user feedback.

What I suggest is to open the discussion on how and why we should start capture users feedback -- especially as an afterwards test and validations mechanism.

I strongly believe that having user response on the completion of a release, a UX change, a hypothesis - will help us define/design/develop better solutions in the future, in less time and we'll have the user as a protagonist in the beginning, middle and the end of the story.

Few diagrams that might help us visualize the product flow

capture-02

lean-ux

hero_image

There is an extensive bibliography that refers to the subject for anyone who wants to learn more..

@mikegianno @yiotaz @codegaze ^^
Thumb or comment if you think has a value tbd

Metadata

Metadata

Assignees

No one assigned

    Labels

    ideationTopic for discussion, brainstormingux-debtSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions