Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effective problem-solving strategies #3821

Closed
SeamusLeonardHPE opened this issue Apr 5, 2024 · 2 comments
Closed

Effective problem-solving strategies #3821

SeamusLeonardHPE opened this issue Apr 5, 2024 · 2 comments
Assignees
Labels
Phase:Downsprint Used for issues that will be worked on during sown sprints. Where:Internal Used in issues related to any internal work.

Comments

@SeamusLeonardHPE
Copy link
Collaborator

SeamusLeonardHPE commented Apr 5, 2024

Clearly articulate success criteria
• Clearly define the criteria for evaluating solutions.
• Use objective yes/no evaluations to determine if a solution meets the criteria.

Seek input and feedback
• Set up focused huddles with stakeholders to address stalled or blocked issues.
• Ask for input and feedback from others.

Connect with others
• Connect with others as soon as possible to collaborate and gather different perspectives.

@SeamusLeonardHPE SeamusLeonardHPE added Phase:Downsprint Used for issues that will be worked on during sown sprints. Where:Internal Used in issues related to any internal work. labels Apr 5, 2024
@oliverHPE
Copy link
Collaborator

Update:
The first outcome of this work is that we need to encourage healthy behaviours regarding 'problem solving'.

For example, these behaviours might include:

  • Writing success criteria
  • Following some form of design thinking process, which might include:
  • Understanding the problem and context
  • Defining the problem
  • Solving at a macro, then micro level
  • etc.

Ideas to encourage this behaviour were:

  • Ticket template (problem solving orientated) - a ticket template that has checks for success criteria, etc.
  • Figma file template, focused on problem solving
  • Introduce a way to classify work as small or large
  • Solve issues (pick-up tickets) only after refinement
  • Consensus / go-ahead on whether to spend the time to refine a ticket or submission to the system

At this point we need to assess which of these ideas, if any, to refine and produce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Phase:Downsprint Used for issues that will be worked on during sown sprints. Where:Internal Used in issues related to any internal work.
Projects
None yet
Development

No branches or pull requests

3 participants