Thomas Frank our (Unofficial) Product/UX Researcher?
- Dominant language
- Dart
- Stars
- 152
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
# _Intro_
When you're a _small_ team/company you need to figure out how to _leverage_ "_other people's time_".
(_not to "make others work for you", by lazily attempting offloading your work/tasks into their inbox ... but by discovering where someone else has already done the research/filtering to distill the knowledge and approximate solving a challenge you are facing..._) 🤔
A _simple_ example that _all_ developers are familiar with is StackOverflow. Someone else has made the effort to ask/answer a question on a technical topic and instead of having to spend _hours_ trying to figure it out for yourself, you write a few keywords into your favourite Search Engine and (_after a bit of term refinement and [frog-kissing](https://www.businessinsider.com/kissing-frogs-2011-5) you_) find an answer that solves your challenge/problem.
When there isn't an _existing_ answer, you create a _new_ question and someone in the wider dev community _selflessly_ answers. That person _donates_ their time to your project/task _for free_ in exchange for a few "reputation points" on the Q+A platform.
# Thomas Frank ?
If you've never heard of him before, see: https://collegeinfogeek.com/start/

"**Start _Here_**!" ... sounds [_familiar_](https://github.com/dwyl/start-here) Thomas ... 😉
Most of Thomas' efforts are in his YouTube channel: https://www.youtube.com/user/electrickeye91

Seriously, you should subscribe to his channel 🔔 it's **easily** one of the **best** on the platform!
(_no idea why his channel user/URL is still **electrickeye91**_ ... 😕 _but it **suggests** he's **born** in [**1991**](https://en.wikipedia.org/wiki/1991)..._)
> If you're still a "student" (_and we **all are** @dwyl_) I'd _highly_ recommend watching _all_ of his "back catalog" of videos. They are _very_ well researched & produced and he _never_ [wastes](https://github.com/dwyl/start-here/blob/master/manifesto.md#your-time-should-never-be-wasted) your life chasing ["watch time"](https://blog.hubspot.com/marketing/youtube-analytics). ❤️
While @TomFrankly is not _currently/yet_ active on GitHub:

That doesn't _matter_ (_for now_) because the fact that he is even _on_ GitHub shows he is at least _interested_ in collaborating on code. 🎉Even though he is not creating _software_, he _is_ doing something else that is _incredibly_ valuable/insightful for the community!
## _Example_ Videos Where Thomas Summarises His [_UX Research_](https://github.com/dwyl/product-ux-research/issues/34)
Thomas does a _superb_ job of summarising his research in a digestible form. e.g:
+ The 10 Best Note-Taking Apps in 2019: https://youtu.be/ay2GvqVH4SM
+ 21 Apps that FORCE You to Be More Productive: https://youtu.be/p-AMooYPO1Y
+ How to Stop Wasting Time - 5 Useful Time Management Tips: https://youtu.be/xwsLuxlbY2w
+ How to Use Habitica to Build Strong Habits and Motivation https://youtu.be/BxxKm7tSL6I
There are _many_ other videos where he mentions specific products.
If we "_mine_" all his videos we will get an _excellent_ insight into his product research conclusions.
# _So_ ...?
So what I'm proposing is: that we make Thomas Frank our "unofficial" Product UX Researcher.
We should all watch his content _and_ read the _comments_ as (_part of_) our "product research". 👀
We _leverage_ the fantastic work that Thomas is doing to _build_ what people _want_.
And eventually, when our app is delivering enough _value_ to the people using it for us to _charge_ for it.
I propose that we form a _partnership_/_sponsorship_ with Thomas' channel. 💡 `#WinWin`
Contributor guide
Research direction
The issue names no repository files, tests, or implementation entry points. Start by reviewing the linked product-ux-research issue, the referenced videos, and their comments to understand the proposed research value. Done would require an agreed, concrete collaboration or product-research plan, but the issue does not define one.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100