Your First 30 Days in a New Role

If you're about to take on a new role, congrats! You've made it through. Outshining the rest to come out on top. Celebrate, you earned it.

As your start date approaches, the descent from cloud nine begins and you're back down on earth (and maybe a tad nervous). It's showtime but where to start?

We love ambition. Your bias for action is why you got hired. We want to hit the ground running and show our worth right away. However, rushing in and imposing yourself is a sure-fire way to become alienated. Burning bridges before they're raised.

Your experience and skills are invaluable, but to leverage them you need a strong foundation. Your first 30 days should be focused on building relationships and a knowledge base (learning all you can).

Work with your manager and get a list of folks to have 1-on-1s with. Identify the key stakeholders. Understand their background, their challenges, working style, and your relationship with them.

Learn as much as you can. Understand the customer, the product, the company. Our strengths, our gaps, your place in it all. The good, the bad, the ugly.

Once you have a solid footing. Take your theoretical learnings and apply them with a "starter project". Something that adds values, allows you to learn how the company works on a deeper level, but low stakes enough to limit risk while you're still learning/experimenting.

You won't change the world in your first 30 days, but you can set yourself up for game-changing opportunities. Connect and learn.

Comments

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark. Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

When Perfect Becomes a Problem: The iCar Story

Let's talk about Apple's iCar, or rather, the ghost of it. A decade. Ten billion dollars. Poof. Gone. Like a puff of smoke from a dream that never quite woke up. They wanted to launch a revolution, a fully-formed, flawless chariot. But revolutions aren't born in secret labs; they're forged in the messy, chaotic crucible of the real world. You don't build a movement by hiding in the shadows. You don't create a product people love by ignoring them. You don't change the world by waiting for perfection. It's about the minimum viable. It's about shipping early, shipping often, and listening—really listening—to the people you're trying to serve. Apple built a cathedral of secrecy. A monument to what might have been. And then, they tore it down. They spent billions on a dream, while ignoring the simple truth: the market doesn't care about your dreams. It cares about solutions. It cares about things that work. So, here's the lesson: stop chasing...

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown . Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks. Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...

Herman Ye

Search