codefordenver / codefordenver/ulc-database
Pivot or Persevere
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Should you Pivot or Persevere?
What feedback did you receive from potential customers?
If the feedback confirmed that you're solving the right problem, for the right people, in the right way, awesome! Let's move forward.
If you received feedback that makes you want to rethink your problem, customer segment, or solution, now's the time.
- Update your lean canvas, and consider going back to the brainstorming and paper prototyping phase to take another shot at it.
Keep iterating until you get feedback that tells you to push on! Keep track of your pivots to share how you arrived at your end solution during your pitch.

Contributor guide
Research direction
The issue body is guidance about pivoting or persevering and names no files, tests, or entry points. Start by determining what repository change is intended and what feedback or acceptance criteria would define completion; no implementation target is currently specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100