Loading...

It’s OK to be seen trying

It’s OK to be seen trying

It’s OK to be seen trying

Somewhere along the way, we started believing that you’re only allowed to speak after you’ve figured everything out. That you can only post once the product is perfect. That you can only ask a question if it’s smart enough, and that you can only contribute once you have “value”: measurable, monetizable, LinkedIn-optimizable value.

And until then? Stay quiet 🤫. Watch. Lurk politely in the back row of the internet.

My suggestion: Let’s kill that idea.

Perfectionism kills participation

It’s not that people have nothing to say. It’s that they’re afraid of saying it wrong.

In many rooms, especially technical ones, there’s this quiet rule: if you don’t already know, don’t speak. And if you do speak, you better be right. Flawlessly, citation-included, TED-Talk-ready right.

The result? Smart, curious people stay silent. Teams lose out on diverse thinking. Communities become echo chambers for the already-confident.

Building in public is a power move (even when it’s messy)

When you share half-baked ideas, drafts, ugly prototypes, something magical happens. You signal that it’s safe to learn here. That trying counts. That progress matters more than polish. You also make space for feedback, collaboration, and the kind of honesty you can’t fake in a keynote. This doesn’t mean performative “look at me failing” posts. It means showing the process. Being real. Building during, not just after.

Yes, the reply guys will show up

The “Actually…” brigade is always ready. The guy correcting your grammar. The one telling you that your take “lacks nuance”. The person who misses the point just to feel smarter. They don’t matter.

If you’re building in public, you will be corrected. But you’ll also connect with the people who get it, the ones who are walking the same messy path, not standing on the sidelines with a red pen.

Your voice matters, even if it shakes

You don’t need to be an expert to contribute. You don’t need to have it all figured out to post something useful. Sometimes, the most helpful thing you can share is the thing you just learned five minutes ago. It’s fresh. It’s real. It’s not “thought leadership”. but it’s thought in motion.

Beginners make the best guides for other beginners. They still remember what it felt like not to know.

Teaching and learning are not separate states

You don’t “arrive” at knowing and then start giving back. It’s a loop. You figure something out. You share it. Someone else teaches you the next piece. Rinse, repeat. The healthiest communities are built by people who are open mid-process. Not the ones holding court, but the ones pulling others up as they climb.

Trying is enough. trying visibly is brave.

“Sometimes I work 40 hours in one day.
Sometimes I need a week to find 4.”

Let go of the myth that it has to look good.
It just has to be honest. Progress beats polish. And showing up, even with a shaky voice and half a plan, is always better than staying silent. So write the post. Publish the prototype. Ask the question. Be seen trying.

Because someone out there is waiting for permission to do the same.

Published on:

Learn more
Need help with this product?

We can help you with It’s OK to be seen trying

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

Luise Freese: Consultant & MVP
Luise Freese: Consultant & MVP

Recent content on Luise Freese: Consultant & MVP

Share post:

Related posts

You are holding GitHub Copilot Wrong!

Most developers think that one can’t really use GitHub Copilot wrong. There is a chat interface that lets you also choose a model, so th...

8 months ago

You are holding GitHub Copilot Wrong!

Part 0 showed why constant prompting, re-prompting, and steering GitHub Copilot feels fragile. Not because Copilot is unreliable, but because ...

8 months ago

Building a Multi-Hierarchy Ticket Classification System (Because Keywords Aren't Enough)

Look, I love a good keyword-based system as much as the next developer. They’re fast, predictable, and when your user says “VPN,&r...

8 months ago

Secretless cross-tenant dataverse access

Client secrets are like hiding your house key under the mat; easy to grab and impossible to audit. Certificates are just slightly better, beca...

10 months ago

How Azure CLI handles your tokens and what you might be ignoring

Running az login feels like magic. A browser pops up, you pick an account, and from then on, everything just works. No more passwords, no more...

10 months ago

How Dev Proxy teaches you to make your apps more resilient

I added Microsoft Dev Proxy to my Mermaid → Dataverse converter, because I wanted to test how it handled rate limits and API errors. What I go...

10 months ago

Building Azure functions that never store secrets — ever

What if your function could hit Microsoft Graph with no client secrets, no certs, and no Key Vault entries? That is exactly what a Managed id...

11 months ago

Introducing Mermaid to Dataverse Converter

Why diagrams matter (and why they usually fail us) Entity-Relationship Diagrams (ERDs) are the universal shorthand for talking about data mode...

11 months ago

Stuck in pilot - Part 1: no foundations, no future

“We just need to test the AI. We’ll figure out the data later.” That sentence has quietly killed more AI pilots than any model failure ever ...

1 year ago

The MVP trap: AI lets you do more, but often worse

There’s a narrative floating around right now: With AI, one person can do the work of a whole team. Code? Done. Design? Prompted. Copy? Gener...

1 year ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.