I Almost Returned the iPhone.

Three days in, I was ready to return it.

I had switched from PC to Mac when I started at Looker. Took about three days before I stopped missing Windows. After that, I never touched one again. The closed ecosystem I had always dismissed as limiting. Once I was inside it, I understood why people never left.

By the time I was building Motif Collective, the rest of my setup had already followed. MacBook Air M5. Apple Studio Display. AirPods Max. I looked around at my desk and thought: what is actually keeping me on Android?

I went through the list. Garmin: works on iPhone. Google Photos, Gmail, Calendar: all on iOS. Nest Hub in the kitchen: still accessible from Google Home on iPhone. Speakers: I cast through Spotify, not natively through Google Cast, so no issue there.

Nothing was holding me. I bought the iPhone.

The first 48 hours were rough.

I had set the phone up without running any migration tools first. I just wanted to get a feel for it. I went through settings, customized everything, started exploring. Then I went looking for the Android migration tool. Apple has one. It only runs during initial device setup, which I had already completed and closed. Resetting a phone I had just spent two hours configuring wasn't going to happen.

So I was on my own. Re-downloading apps. Hunting for the back button that no longer existed. Getting annoyed at gestures I didn't ask for and missing the ones I had used for thirteen years. By end of day one, I was doing the math on whether I could get to the Apple Store and be back on my Samsung before morning.

I didn't go. I had a road trip to Michigan the next day. My dad's birthday. A long weekend at a lake house with the family. There wasn't time.

The moment I stopped comparing

I was packing for the trip, AirPods Max on, Spotify running. And then I noticed something.

I was dancing. Not nodding, not tapping my foot. Actually dancing while throwing clothes into a bag. It took me a minute to figure out why.

Lossless audio. The iPhone and AirPods Max can play lossless Spotify together, and I had never experienced that before. The song had a serious kick drum. On every phone I had owned for thirteen years, that drum was a compressed thud. On this, it felt like standing next to the kit. Every layer, every reverberation. I had been listening to music through a filter for so long I didn't know what I was missing.

Then came CarPlay on the drive up. I live in Chicago, so I know the highways. Eight lanes collapsing to two near O'Hare, construction everywhere, exits you have to be in position for a mile early. CarPlay switched to an aerial view of the road, marked every lane, and started giving me advice before I even got close to the decision points. Not turn-by-turn. Predictive. Telling me what was coming before I had to react to it. I didn't know I wanted that. It was significantly better.

The lake house

My dad is big into music. We had Spotify going the whole weekend. I was watching YouTube before bed, using Maps to find dinner spots, looking things up constantly. Normal phone behavior.

What changed was the other direction.

I wasn't getting buzzed every few minutes by things that didn't matter. I wasn't making a silent calculation every time my phone vibrated about whether to look at it. The focus modes and the way Apple Intelligence filtered notifications meant the phone was making those calls for me and getting them right. I was present at my dad's birthday without having to manage my own attention manually. That sounds like a small thing. It wasn't.

At the end of the weekend, the battery had barely moved. Two days of real use. I hadn't conserved anything.

“I had been this close to returning a phone that was, by every actual measure, better than what I had.”

Not because it was bad. Because the first two days were uncomfortable and I kept trying to use it like a Samsung.

This is not a phone problem

Here is what I kept thinking about on the drive home.

A company runs a six-month RFP. They score vendors, document requirements, build an ROI model, sign a contract. They implement the new tool. Nobody uses it.

Leadership blames the operators. Why are they so resistant? The operators are frustrated because someone handed them something new, told them it was better, and moved on. Nobody asked what was actually hard about their day. Nobody showed them what the tool could do for the specific things they were already struggling with.

So the organization does what feels safe. They replicate the old workflow inside the new tool. They map the old reports to new dashboards. They recreate the process they already had, just in a different interface.

If it were a true one-to-one replacement, you wouldn't have needed to migrate. The whole point was that something better was possible. Now you've buried that under the familiar.

I was never going to hear lossless audio if I was too busy being annoyed about the back button.

Looker, 2017

Back then, Looker was a small company with a new idea: self-service business intelligence built for the people who actually needed the data, not just the engineers who could write SQL. Selling it meant sitting with someone long enough to understand what they couldn't do today. What decision they were making slowly, or not at all, because the right information wasn't accessible.

You had to find the real problem before you could show someone why Looker addressed it. And because the team was small, you stayed close after the deal closed. You knew the specific frustrations of the VP of Finance three months in. You had had the personal, uncomfortable conversations that got underneath the surface requirements. You were invested in whether it actually worked.

That feedback loop was tight. The relationship was real.

Then Google acquired Looker. The deals got bigger, the enterprises more complex, the partner ecosystem more involved. You started handing off what you had sold to someone who knew the product well but hadn't been in those early conversations. They hadn't navigated the pain. They were starting from a product spec, not a relationship.

Nothing was wrong with the people. It was structural. Scale had broken the personal loop.

What we're building

That's the thing Motif Collective exists to bring back.

The scrappiness. The personal investment. The ability to go in, understand what someone is actually carrying, and build specifically to that before anyone has written a line of production code. The part that gets skipped when timelines compress and everyone just wants to ship.

We do that at two altitudes at the same time: strategy at the leadership level and daily friction at the ground level, with the same team holding both. No handoff to someone who wasn't in the room. No waterfall delivery before anyone has heard from real operators. You ship small. You learn fast. You build from what's actually true.

If you don't know you're going to make someone's job easier before you've built anything, you're not ready to build yet.

Ground Truth, Innovation in Name Only, One Pattern, Three Industries. Different problems. Same approach.

---

Apple didn't update my phone between day one and day three.

Nothing changed. I just stopped trying to use it like a Samsung.

That's the whole problem. Better software has never once solved it. You close it by understanding what people are already carrying before you tell them what's possible.

That's the gap. That's what we built this for.