1. Home
  2. Detail

@trickshotdav: What are the odds of this? 😂 #fyp #trickshot #viral #lucky #candleshot #pingpong

Davide🇨🇦🇮🇹
Davide🇨🇦🇮🇹
Open In TikTok:
Region: CA
Wednesday 30 December 2020 23:37:31 GMT
39258
2371
26
4

Music

Download

No Watermark .mp4 (0.86MB) No Watermark(HD) .mp4 (0.86MB) Watermark .mp4 (0.84MB) Music .mp3

Comments

situational.update
. :
I wont follow you… I already did😂😁😁😂
2021-01-02 13:28:37
2
yusufbekermama
yusufbekermama :
Can you plzz do a totorial on how to start to do trick shots plzz🥺🥺🥺
2020-12-31 06:47:44
2
cyross_
🦆 :
OMFG btw first😂😳
2020-12-30 23:40:19
2
uvejs470
uvejs470 :
3rd LUL😂
2020-12-30 23:42:35
2
creamymcfreeme
CreamyMcFreeMe :
NOOOOO
2020-12-30 23:41:34
2
mr.mv.7
MV :
HOW DID THIS FLOP
2020-12-31 10:24:45
1
jesuschristoffa
Jesùs Christoffa :
😳 I fell off my bed
2021-07-18 18:25:14
0
trickshotzac
TrickShotZac :
No way 😳
2020-12-31 03:45:46
1
_muhamed.k
zero4🇽🇰 :
Oooo this (serbian, bosnian, kroatian) acsentttt
2020-12-31 01:02:24
1
user1537296149413
User37 :
I’m one of the top five people to comment first 😅
2020-12-31 00:07:21
2
peter_pallo
Peter Pallo :
O.M.G.😂😂😂 you are so Lucky. How much time you spent there ?😂
2020-12-31 08:57:45
0
To see more videos from user @trickshotdav, please go to the Tikwm homepage.

Other Videos


#looksmax #щп #рофл
#looksmax #щп #рофл
Deep down I know that I’ll see you again ❤️
Deep down I know that I’ll see you again ❤️
Why “asking ten people” can kill an idea • Dilution of vision: When you solicit broad opinions before you’ve clarified your core hypothesis, you get ten different directions and end up with a compromised, generic version. • Premature optimization: Early feedback often focuses on surface details (wording, colors, edge cases) instead of whether the underlying problem and solution are worth pursuing. • Social risk aversion: People tend to point out risks more than possibilities, especially if they’re not invested in your success. That skews the signal toward “why this won’t work.” • Decision paralysis: Conflicting advice creates uncertainty, which leads to endless tweaking instead of shipping a testable version. When asking people helps instead of hurts The problem isn’t feedback; it’s unstructured, premature, and unfocused feedback. • Ask the right people: Talk to people who actually experience the problem you’re solving, not just colleagues or friends who want to be helpful. • Ask at the right time: • Very early: test the problem and value proposition (“Does this matter to you?”). • Mid-stage: test usability and clarity (“Can you do X without help?”). • Later: test pricing, positioning, and scale. • Ask the right questions: • “What’s the last time you faced this problem?” • “How do you solve it now?” • “What would make this 10x better?” Avoid “Do you like this idea?” which invites polite, low-signal answers. A better pattern than “ask ten people” Instead of “ask ten people what they think,” try: 1. Write a one-paragraph hypothesis: • Who has the problem? • What is the problem? • What is your proposed solution? • What would count as success? 2. Talk to 3–5 target users with that hypothesis in mind, focusing on their behavior and pain, not your solution’s features. 3. Look for patterns, not opinions: If multiple people independently describe the same pain and current workaround, that’s a strong signal. 4. Decide, then test: Make a clear decision based on patterns, then run a small experiment (landing page, prototype, pilot) instead of re-opening the debate.
Why “asking ten people” can kill an idea • Dilution of vision: When you solicit broad opinions before you’ve clarified your core hypothesis, you get ten different directions and end up with a compromised, generic version. • Premature optimization: Early feedback often focuses on surface details (wording, colors, edge cases) instead of whether the underlying problem and solution are worth pursuing. • Social risk aversion: People tend to point out risks more than possibilities, especially if they’re not invested in your success. That skews the signal toward “why this won’t work.” • Decision paralysis: Conflicting advice creates uncertainty, which leads to endless tweaking instead of shipping a testable version. When asking people helps instead of hurts The problem isn’t feedback; it’s unstructured, premature, and unfocused feedback. • Ask the right people: Talk to people who actually experience the problem you’re solving, not just colleagues or friends who want to be helpful. • Ask at the right time: • Very early: test the problem and value proposition (“Does this matter to you?”). • Mid-stage: test usability and clarity (“Can you do X without help?”). • Later: test pricing, positioning, and scale. • Ask the right questions: • “What’s the last time you faced this problem?” • “How do you solve it now?” • “What would make this 10x better?” Avoid “Do you like this idea?” which invites polite, low-signal answers. A better pattern than “ask ten people” Instead of “ask ten people what they think,” try: 1. Write a one-paragraph hypothesis: • Who has the problem? • What is the problem? • What is your proposed solution? • What would count as success? 2. Talk to 3–5 target users with that hypothesis in mind, focusing on their behavior and pain, not your solution’s features. 3. Look for patterns, not opinions: If multiple people independently describe the same pain and current workaround, that’s a strong signal. 4. Decide, then test: Make a clear decision based on patterns, then run a small experiment (landing page, prototype, pilot) instead of re-opening the debate.
😮‍💨😅🥳
😮‍💨😅🥳

About

Legal