"When you talk to people about breaking them down, they feel like they're going to get flattened. This negative perception of breaking down siloes can impact the organization's ability to solve the siloes in the first place."
When you take the leap of faith to bring your vision, your idea, to life and start your company, you wear many hats and take on many tasks. You develop the business plan and deck pitch, help build a great product or service offering, create and implement the marketing strategies, make sales, handle customer service and get take-out for everyone during the late nights they're working.
I don't take founders here for exercise. I take them here because the controlled environment of a boardroom practically demands rehearsed answers. The trail does not. I don't prepare a script for these walks. In fact, that's the point. The pitch is already done; I know the metrics. Now I want to know the human.
You must be a TalkNats Subscriber to access this content. Subscribers have access to exclusive content on the TalkNats website and can engage in discussions with other Nats fans. First two weeks are free and then you will be billed $3.99/month. Cancel anytime. Secure payments using Stripe. If you are already a subscriber, simply log in using the form below.
At the height of my success as a realtor in Washington, there was a moment when I was being offered incredibly high-valued listings. People were calling me and offering me opportunities that I had worked so hard to get, and in that moment where one might expect me to feel victorious or excited, I felt nothing. I received a call and was offered an amazing listing, in one of the best locations in Washington and my first thought was, no.
That pause is where the real work begins. Not in polished sketches or carefully worded summaries, but in the willingness to stop moving long enough to ask questions that haven't yet been surfaced. Why does this exist? What is it meant to do? Who is it actually serving?
Every major leap in my career, and every transformation I've led, began with a decision that involved risk, uncertainty and discomfort. If you're a leader, you've likely faced similar inflection points. Years ago, at Washington State University, we launched one of the first fully online undergraduate Management Information Systems (MIS) programs. At the time, it was uncharted territory. Few business schools had ventured into online learning, and many questioned whether students or employers would take the format seriously.
We're fortunate to stand on the work of giants. Every time we cross a suspension bridge or hear a brilliant piece of music, we experience the spark of someone else's genius. We don't need to understand every theory to benefit from it - and the same is true in building a business. You don't need a computer science degree to think like an engineer - but doing so can help you build smarter, faster and with fewer mistakes.
As an Asian-American kid growing up to an immigrant mom in North Carolina, I was taught to follow the rules (no exceptions). I was a Boy Scout, graduated top of my class and was hired by Goldman Sachs immediately after graduating undergrad. I had followed what I thought was the "right" path. I was living in the greatest city in the world (New York City, of course) and working at one of the best companies in the world ... but none of it felt right.
But if you're innovating within your industry, it's a problem you should expect and prepare for because it means having to operate in two realities-the internal reality where you know the challenges in your industry and how you're going to solve them, and the external reality where nobody else has recognized the problem that needs to be solved. In a highly regulated industry like healthcare, safety, and stability create an inertia that often works against innovation.
A colleague and I launched a new company after our previous employer closed. We divided responsibilities so she handled manufacturing and distribution while I managed digital content and marketing. My side of the business grew steadily. But within six months, her operational area began to falter. I began to step in to keep physical projects moving, and key infrastructure on her side wasn't maintained. Despite having access to shared digital project management tools, she frequently framed it as a communication problem.