Not resisting technology
She works on a team. She could be in operations, finance, customer success, people, or any function that isn't engineering. Her team uses AI. She doesn't. Not because she's technophobic or resistant to change. She just opted out.
Here's why: the first time she tried AI, she opened a blank text box and had no idea what to put in it. The result came back wrong. She tried again. Same problem. After a few attempts, she concluded that AI wasn't for her. Maybe it worked for other people, people who knew how to prompt. She wasn't one of them. She didn't trust the results. She stopped trying.
Now her coworkers use AI. They move faster. She doesn't. She watches them use it and thinks, "That's not something I do." It's not that she decided not to. She just can't find the entry point.
This is what opt-out actually looks like. Not loud rejection. Quiet absence.
The blank page problem
Every AI tool assumes you know what you want to ask. They all start with a text box and an expectation that you'll fill it. For someone who doesn't know how to prompt and whose early attempts came back wrong, the text box feels like a test she already failed.
The other way people learn is by watching. When her coworkers use AI, she can see them doing it, but she can't see the prompts they wrote. She can see the output. She can't see the thinking that got there. So when she goes to try it herself, she's back at the blank page with no reference and no one to ask.
The experience compounds the original doubt. AI works for them. It doesn't work for her. The difference must be her.
How it changes with Wind Stream
She doesn't join a solo session to prove she can prompt. She joins a session that's already in progress. There's already context in the room. There's already a prompt that worked. She asks a question right there, in the conversation, next to the output it produced. She doesn't have to start from nothing.
At some point, she's contributing to the session. She suggests an edit to something. She watches it change. She sees the output adjust. She stops thinking of this as using AI and starts thinking of it as the place where the team works.
She's not converted. That's the wrong word. She just stops opting out.
What changed
She stopped avoiding AI. That's not the same as "became an AI power user." It's more honest and more real.
Teams that brought this person into shared sessions saw:
She stops re-inventing the wheel. She's not starting from a blank page. She's working with context that's already there.
She learns the prompts that work. Not by reading tutorials. By seeing them in context, next to the output they produced, used on a real problem she cares about.
She contributes without performance anxiety. It's not "she tries AI." It's "the team is working on this and she's in it."
AI stops being a skill she needs to acquire separately. It's just how her team works.
A real story
"I didn't think I was an AI person. I just started working in the same session as everyone else and I didn't notice when I stopped thinking about it as using AI. One day I was editing a prompt and I realized I was the one editing it, not asking someone else to."
Made-up Operations Manager, 120-person company
