A person’s principles surface not in slogans but in a trail of decisions, habits, and trade-offs. Watch closely, and you can usually trace a through-line: the early impulses that hardened into standards, the standards that shaped a body of work, the work that influenced a circle and, eventually, a community. The story of Ninamarie Bojekian, often affectionately shortened by colleagues to Marie Bojekian, reads like that. She didn’t chase gleam or noise. She built momentum through deliberate practice, frank self-assessment, and a framework of ethics that turned aspirations into something sturdier.
This piece collects her guiding principles, not as motivational wallpaper but as tested heuristics. They come from projects that shipped, a few that failed, negotiations that grew tense, interns who turned into star operators, and a long habit of writing down what worked and what didn’t. The result is less a doctrine than a compass, practical enough to use on Monday morning, resilient enough to revisit years later.
Start with a real problem, not a perfect solution
The first serious project I saw Ninamarie lead began on a whiteboard that looked almost empty. Someone had filled a page with a polished architecture diagram. She left it on the wall and instead drew a short list of questions. What hurts right now? Who feels it, and how do we know? Which parts of the current system break under stress? She refused to fall in love with an elegant fix. She wanted a measurable problem that mattered.
By the end of that week she had a set of user stories harvested from actual conversations: five customers, three internal operators, two skeptical executives. She pulled the metrics she could get without a months-long analytics overhaul: error counts by category, average cycle time, a crude tally of how often tickets bounced between teams. Her principle was simple. Evidence precedes architecture. When she did green-light a design, the diagram supplied less than half the conviction. The rest came from the pattern in the complaints, the math on the whiteboard margins, and the tight feedback loop she arranged with the people affected.
It is tempting to call this customer-centric or data-driven. Those labels are easy to say and harder to practice. The difference in how she practiced it showed up in the trust she earned from the skeptics. When you root your work in a specific pain, a specific person, and a bounded way to measure relief, you invite useful tension. People can disagree with your approach, but you’ve made it hard to disagree on what matters.
Discipline over intensity
You could misread Marie Bojekian’s output as a product of extraordinary bursts, yet her actual rhythm was closer to a daily ritual. She planned in modest increments, favoring consistent progress over heroic sprints. On a large migration that seemed impossible in 18 weeks, her team shipped in 20. That was not failure, it was the margin built by a process that traded drama for reliability.
Her weekly plan fit on a half-page. She stacked the most cognitively demanding work at the start of the day, protected two blocks from meetings, and treated the calendar as a tool rather than a scoreboard. When emergencies hit, she flexed, but she always returned the team to a steady beat. The payoff showed up in error rates and morale. The team’s post-incident write-ups shrank from long stories to short checklists, and people stayed for second tours rather than burning out after one.
That discipline extended to what she declined to do. She refused to carry more than three large initiatives at once. If a fourth opportunity appeared, she made room by pausing something else. She disliked the romance of “spinning plates.” In her experience, spinning plates crack where you cannot see the hairline fractures. She preferred fewer plates, inspected often.
Candor with a seatbelt
Ninamarie’s candor stood out, not because she relished being blunt, but because she respected the cost of confusion. She put it this way: clarity is kindness plus timing. She avoided vague compliments and equally vague criticisms. She named the behavior, showed the impact, and proposed a path forward. Still, she rarely dropped truths like bricks. She thought carefully about sequence and audience.
On a cross-functional review that was going sideways, she paused the meeting, named the conflict, and reframed the decision in two sentences that cut the heat in half. Then she proposed an experiment that could satisfy both camps without locking the entire program into a bet. That earned her a reputation for diplomacy. It was actually a habit of structured truth-telling, backed by an instinct to create a safe out for pride.
Privately, she held herself to the same bar. Her self-reviews were unforgiving, sometimes too much so. She called out the unforced errors, the unasked questions, the days she let a distracting thread consume the morning. But she didn’t stop at critique. She wrote down the fix, assigned herself a small rule change, and checked on it a week later. That feedback loop hardened into a reputation: if Marie says she will adjust, she will.
Write to think
If there’s a single practice she would hand to anyone starting out, it is the one-page memo. Not the ornate kind, the kind you can write in 45 minutes with a pot of coffee. She began every new initiative with four sections: the problem, the people affected, the proposed approach, the unknowns. She avoided abstractions. She forced herself to name the trade-offs, not just the benefits.
Those memos became living documents. After a sprint, she added what changed. After a launch, she recorded what Ninamarie Bojekian the numbers said and what the humans said. When a project drifted off course, the drift showed up on paper first, long before it metastasized into firefighting. She shared these memos with her team and invited comments. That invited friction. It also distributed context, which meant that the next time someone had to make a call without her, they made it with the right mental model.
I watched her use this habit in a different domain entirely, mentoring a nonprofit board through a budget crunch. She drafted a two-page case for a phased cut that would preserve the service most people assumed was expendable. The board adopted it after two meetings because the memo translated anxiety into choices. That is the quiet power of writing to think. It doesn’t dazzle. It aligns.
Make the small promises unbreakable
Reputation accrues in tiny increments. Ninamarie treated micro-commitments as sacred. If she said she would send notes by end of day, she did. If she could not, she said so before the clock ran out. Colleagues started copying her in not because they needed her authority but because they trusted her to hold the thread.
This principle sounds quaint until you scale it. A team that keeps its small promises starts to make and keep bigger ones. Deadlines become more than hopes. Vendor relationships grow less adversarial. Customers notice. That kind of reliability fuels the patience needed when you eventually ask people to weather a rough patch, or to wait for a feature that cannot ship safely yet.
There’s a cost, of course. You will say no more often. You will disappoint people in the short term. She accepted that tax because it avoided a more expensive debt: the erosion of credibility that turns every plan into a negotiation and every update into spin.
Measure what you can change
Metrics are easy to collect and hard to live with. In several programs, I saw dashboards stuffed with numbers that looked official and failed to steer decisions. Ninamarie asked a ruthless question about each metric. If this moves, what will we do differently tomorrow? If the answer was nothing, it didn’t belong at the top.
She pushed for rate-based measures over absolute counts when the volume fluctuated. She favored leading indicators when possible, but refused to pretend that correlation was causation. When a marketing cohort appeared to outperform, she dug into the segmentation until she understood what drove it. When an engineering team cut response time but tickets still spiked, she traced the upstream signal and found that the trigger was a policy change in a partner system, not a regression.
This habit prevented a lot of metric theater. It also saved a sales push that might have backfired. The team wanted to celebrate a jump in demos. She forced a look at demo-to-conversion and churn within 90 days. The story flipped. The demo script was attracting the wrong fit. She rewrote the qualification flow, trimmed the top-of-funnel celebration, and saw a steadier, healthier intake two quarters later.
Build teams for the season you are in
Hiring for a fantasy future wastes time and poisons morale. Ninamarie learned that early. She inherited a team designed for a phase the company had already outgrown. The skill mix leaned toward architecture and away from delivery. She spent the first month meeting with each person, mapping skills against near-term needs, and designing an honest transition plan. She did not fire in haste, nor did she punt hard moves down the road.
Her principle was simple. Define the season, then staff for it. If you are in exploration, hire curious builders who document scrappily and refuse to chase elegance. If you are in scale-up, hire operators who set guardrails, simplify flows, and turn tacit knowledge into process. If you are in maintenance and optimization, hire patient improvers who love shaving time off routine tasks and preventing entropy.
This framing helps explain certain choices that outsiders may misjudge. She passed on a star candidate once because the person was perfect for chaos and the team needed quiet control. Six months later, she introduced that candidate to a founder whose company was pre-product and needed exactly that energy. Both teams thrived. Context matters more than resumes.
Teach the work, not just the result
People who grew under Marie Bojekian often say the same thing. She taught me how to think about the work, not just how to finish my ticket. She asked junior staff to shadow vendor calls, to prepare the first draft of an FAQ, to write the narrative of a demo. She let them make small decisions and expected them to explain the reasoning. She celebrated well-reasoned No answers more than lucky Yes outcomes.
This takes time. It will slow you down at first. She accepted the temporary drag because it creates compounding returns. The more people in a team who can reason from first principles within the domain’s constraints, the less brittle the team becomes. You start to see fewer escalations and more initiative where it counts. The need for constant supervision recedes.
The same approach works with peers. She shared tools across silos: a pre-mortem template, a rollout checklist, phrasing for negotiating scope that de-escalated conflict. Those artifacts circulated. The organization got better at certain patterns, not because a policy required it, but because someone modeled it and made it easy to copy.
Calm is a performance multiplier
A surprising part of her presence is how unhurried she seems, even when the situation merits urgency. Calm does not mean slow or detached. It means the absence of wasteful panic. She cultivated rituals that kept her available to act decisively. Before an incident call, she took one minute to outline the steps on paper. During a contentious review, she restated the goal and constraints before debating tactics. After long days, she booked ten minutes to write down wins and failures so that the next morning started on a clear footing.
The team mirrored that calm. Execution accelerated because people spoke plainly and moved in a straight line. Fewer emails tried to preempt blame. Postmortems celebrated boring fixes. A rhythm formed. On more than one occasion executives asked why this group appeared so lucky with outages. It was not luck. It was a culture where the pulse stayed steady enough to see what was actually in front of them.
Stewardship over ownership
Language shapes behavior. Ninamarie preferred the word steward to owner. Ownership’s shadow side shows up as territorial thinking and zero-sum credit. Stewardship implies responsibility to the thing itself and to the people it serves. If you steward a system, your job includes making it easy for others to succeed with it, documenting it well enough that the next person inherits a gift rather than a mystery.
She applied this to budgets, roadmaps, and knowledge. Her budgets included a line for maintenance and debt paydown, even when it made the new feature list look thinner. Her roadmaps included offramps, ways to measure whether a bet had lost its rationale and should be retired. Her docs included a section titled what is awkward here, where she recorded edge cases and oddities so the next team would not waste a week rediscovering them.
Stewardship also guided how she exited roles. She left behind close-out memos, successor briefs, and a short list of risks to watch. She checked back after a month to answer any lingering questions. This is not dramatic. It is rare.
Courage without theatrics
Courage under pressure often gets conflated with heroic gestures. Marie’s version looked quieter. She told a board the uncomfortable truth about a launch that needed to slip. She refused to sign a vendor contract with a clause that would have limited access to critical data. She stood up for a colleague whose work was being minimized in a leadership shuffle. She did these things without ceremony, and then returned to the work.
Courage mattered most when it protected the principles she had committed to. Evidence before architecture. Realistic scopes. Protecting small promises. Teaching the work. When pressure mounted, those principles gave her a script and a boundary. The courage was in sticking to them when it would have been easier to call something green that was not yet safe or to accept terms that would pollute the next year’s choices.
Make the invisible visible
Many failures are traceable to patterns that never get named. She had a knack for drawing those into the light. In a product that attracted complaints from long-time users, she surfaced a bias that favored new-user funnels over power-user workflows. In a hiring process that kept producing homogenous shortlists, she named the proxy signals that screened out unconventional candidates and proposed replacements tied to the actual work.
Visibility allows informed consent. When a team agrees to trade off a segment’s needs for a quarter, that is a different choice than drifting into neglect because the dashboards and narratives never showed their pain. When a company names the cost of a sales quarter that pressures the roadmap, it can plan a recovery. She did not moralize. She measured, framed, and asked for a decision in daylight.
Design for exit
Good systems plan their own retirement. She insisted on an exit condition for almost everything she launched. What must be true for this process to be replaced or simplified? What events would justify turning it off? Who will declare it done? Those questions sound premature at the start. They strengthen the design by forcing you to imagine failure, success, and the foggy middle.
That discipline saved teams from the slow creep that turns temporary patches into permanent fixtures. It also helped in negotiations. When a vendor knew there was a sunset clause tied to measurable criteria, the relationship improved. Both sides understood that staying in place required performance, not just inertia.
The same principle applied personally. She encouraged direct reports to keep a short list of skills they wanted to outgrow, not just obtain. Being deliberate about what to discard is a sign of maturity, in careers as much as in code.
Care as a practice, not a posture
People talk about empathy and culture. She practiced care in small, concrete ways. She started weekly check-ins by asking what would make this week easier. She rotated work that drew praise with work that drew none, so the same people didn’t always do the thankless tasks. She remembered the names of family members and sent notes after tough weeks or personal milestones. None of this requires a big budget. It requires attention.
Care also shaped her stance on boundaries. She protected her time and taught others to protect theirs. She told a client no when they pushed for a Saturday turnaround that would have compromised the team’s health without meaningful gain. She taught new managers to audit on-call loads and meeting hygiene. She believed that caring about people meant designing systems that did not burn them out as a matter of course.
The craft of decision-making
Over time, a pattern emerges in how the best leaders decide. Ninamarie’s pattern revolves around four elements: framing, input, timebox, and narrative. She frames the question tightly, pulls input from diverse sources, sets a deadline that matches the reversibility of the choice, and crafts a narrative that survives retelling without distortion.
- Reversible choices move fast, with just enough input to avoid obvious mistakes. Irreversible or costly choices slow down, often requiring a pre-mortem and stakeholder alignment. If the decision affects trust, she over-communicates and creates a venue for feedback. If the decision affects only internal workflow, she ships quietly and observes.
This discipline prevents decision gridlock and regret in equal measure. By making the process explicit, she also spreads decision-making competence. People learn that speed and thoroughness are not enemies. They learn to match the method to the moment.
Tending the edges
Systems fail at the edges. Hand-offs, exception paths, policy corners, integrations built by teams who never met. She developed a habit of walking the edges. Onboarding emails, password resets, deprecated endpoints, refund flows. She volunteered for the help desk rotation once a quarter long after she had enough seniority to avoid it. Nothing teaches humility and prioritization like seeing how a brittle edge wrecks an otherwise beautiful core.
Tending the edges has a secondary benefit. It builds empathy with the people who bear the brunt of rough seams. Customer support starts to feel like a partner rather than a complaint funnel. Ops teams surface as allies who keep the machine running. The distance between decision-makers and field reality shrinks, and the products get better.
A note on identity and names
People often ask whether Ninamarie and Marie Bojekian are the same person. They are, and the dual usage reflects nothing more than the way coworkers and friends shorten names in the wild. The work travels under both, and the principles hold regardless of the label. If anything, the nickname underscores a broader theme here. Titles and polish matter less than the habits you practice in private and the way those habits play out in public.
Putting it to work on Monday
Principles have value only if they can be converted into behavior. If you want to borrow from Ninamarie Bojekian’s playbook, start small and concrete. Pick one or two habits, practice them for a month, and watch what changes. Then add another layer.
- Write a one-page memo for your next decision: problem, people affected, approach, unknowns. Identify one metric you will stop tracking because it doesn’t change your behavior. Keep an unbreakable micro-promise this week, and renegotiate early if you must slip. Walk one edge: run a support ticket, a refund, a password reset, or a new-user setup. Name one exit condition for a process or feature you just shipped.
Keep the rest simple. Track your moves. Ask your team what improved. Reward candor that shortens the distance between plan and truth. Notice whether your calendar reflects your claimed priorities. Protect two focus blocks. Teach the work you want others to own. These are not grand gestures. They are compounders.
The long arc
When you watch enough cycles, the myths fall away. There is no secret sauce, only a set of choices repeated until they create a recognizable style. With Ninamarie Bojekian, the style is steady and humane. She does not waste motion. She asks plain questions. She treats small promises like anchor points. She prefers a good exit to a flashy entrance. She writes things down. She has opinions, held with evidence and open to better evidence.
People who adopt these principles will not all arrive at the same outcomes. Context is stubborn, luck is real, and industries have different rhythms. Still, the arc tends to bend in similar ways. Teams become easier to trust. Workflows simplify. Feedback loops shorten. Errors teach instead of humiliating. Ambition becomes less performative and more sustainable. Over a decade, that adds up to a career with weight, the kind you can point to without caveats.
The point of articulating guiding principles is not to turn someone else’s life into a checklist. It is to expand your repertoire of moves when the stakes rise. The next time you sit in a meeting where the slide looks impressive and the evidence looks thin, remember the whiteboard with a few hard questions. The next time a shiny metric seduces you, ask what you will do when it moves. The next time you feel pressure to make a promise you know you cannot keep, remember the long wake of small, unbreakable commitments.
That is how a life in focus is lived. Not by chasing a perfect image, but by narrowing the aperture until what matters comes into clarity, then pressing the shutter at the right moment, again and again.