To Post or Not to Post?

I’ve never been great at staying quiet. Just ask my shirt, it literally says, “I have the right to NOT remain silent.” And honestly, that’s always felt true. So it should come as no surprise: I won’t be staying quiet during this project either.

As you might have read in some of the earlier posts, I spent a while debating whether I should share this publicly at all and where. Part of me felt like it might be a little… much. A little attention-seeking. A little “who does she think she is?”

But then again, maybe that’s just the voice of self-doubt trying to keep things comfortable. Because here’s the truth: I know this project is a bit bold. I’m 19, trying to get interviews with some of the most powerful people in business, based on nothing but curiosity and a little bit of determination. I don’t have a perfect track record. I don’t have connections. I don’t even have a backup plan if this doesn’t work.

I’ve gone back and forth on this. It’s scary to share something before it’s done, especially when there’s a real chance it might fail. What if the CEOs never reply? What if the interviews lead nowhere? What if the insights are just… mediocre? What if no one cares?

But that’s exactly the kind of thinking I’m trying to unlearn.

This project is not about proving something. It was about figuring something out. It’s about learning and sharing that learning in real time, not just after I’ve cleaned it up and tied it in a bow. Honestly, I think we need more of that. Because when I was trying to figure out what to do this summer, I didn’t see a lot of people doing things like this, especially not people my age. So maybe that’s why I’m sharing this.

So yes, I’m publishing this.

Not because it’s perfect.

But because it’s honest.

Because I believe it’s worth documenting what it looks like to build something before you know how it ends.

As for the format… I’ve decided on this blog that you are reading. Not a polished newsletter, formal research paper, or a documentary, but a real-time, behind-the-scenes look at how this project is actually unfolding.

Why? Because I didn’t want to just share the results once everything was neat and impressive. I wanted to document the messy middle, too. The uncertainty. The setbacks. The small (and hopefully occasionally big) wins. I want a place for the things I’m learning, not just about AI and consulting, but about taking initiative, getting ignored, staying curious, and figuring things out as I go.

I want my voice to shine through. This project is serious, but I’m not treating it like a corporate report. I’m 19, figuring things out, and writing as I go. Hopefully, it’s a little insightful, a little entertaining, and maybe even helpful for someone else trying to do something bold:)

And if you’re reading this? Thanks for being part of it.

Because hopefully this will be pretty cool!

Good luck June, you got this!

Best,

-June