@madi.gets.fit: I mean.. am I wrong? Look, most of the time I’m just getting my veggies over with 😅 And honestly, I think that’s ok! I mostly just eat veggies because I know they’re good for me and my body needs them, not so often because I think they’re really yummy. I’ve learned a lot on my health journey, and this is one of those things! Share this with a friend who needs to eat more veggies!! #healthjourney #healthandfitness #healthylifestyletips #highfiber @Madi | Healthy Mom Era 🦩 @Madi | Healthy Mom Era 🦩 @Madi | Healthy Mom Era 🦩

Madi | Healthy Mom Era 🦩
Madi | Healthy Mom Era 🦩
Open In TikTok:
Region: US
Wednesday 30 September 2026 00:33:54 GMT
701
92
9
1

Music

Download

Comments

mompreneurem
Emily Williams :
Taking freaking notes! 📝
2026-10-03 19:31:34
3
bennjarlow
Jenn :
I do this but with cheese and wine. Works great!
2026-09-30 00:39:24
2
bumbumbeedumdum
chopinesque :
I like it!
2026-09-30 00:38:10
3
fat_and_fit_mom
Fat and Fit Mom 🇨🇦 :
Shut the front door that’s so smart.
2026-09-30 21:41:57
0
mompreneurem
Emily Williams :
So smart
2026-10-03 19:31:39
1
To see more videos from user @madi.gets.fit, please go to the Tikwm homepage.

Other Videos

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