Field Notes from the Language Age

Observations from live systems where humans, technology, context, and intelligence meet.

A practitioner’s record of what happened, what changed, and what remains open. Revisited as understanding grows.

JIM JORGENSEN · A WORKING NOTEBOOK

James Jorgensen James Jorgensen

Field Note 05 — The First Hill

Field Notes from the Language Age

The Improvement Plan

Before the Next Hill

I grew up in the future. Well, not exactly. But I spent a good part of my childhood imagining it.

I remember sitting with volumes of the Encyclopedia Britannica, reading about science, looking at illustrations of space exploration, and flying cars. Video telephones. Computers that could think. Machines that might do things humans couldn't.

Somewhere in the middle of all that, Star Trek appeared on television. Captain Kirk could talk to his ship's computer, ask it a question, and receive an answer. People communicated across enormous distances using handheld devices. A machine could transport somebody from one place to another. The future was so exciting to me.

The world I was living in was considerably less sophisticated at the time. Telephones were attached to walls. Long-distance calls were expensive. Pay phones went from a nickel to a dime and eventually a quarter. And if somebody wasn't home when you called, you tried again later instead of leaving a voice mail. Gasoline was just gas, and I did not even know there was lead in it. The television only had a few channels and went off the air at 11 PM.

A few years later I was riding my bike on a paper route dreaming about watching bands play live and traveling through space as an astronaut. In another flash around 1976, I remember a friend and I setting up a sound system together. I didn't know it then, but I'd found something that would occupy much of the next fifty years of my life. I had no idea how my life would witness the many changes that would soon come in technology, communication, and lifestyle.

Computers moved from universities and corporate offices into homes. Analog recording gave way to digital. Cellular telephones appeared, initially looking more like something you'd carry over your shoulder onto a construction site than put in your pocket. The internet arrived in our everyday lives. Then email, websites, portable music, smartphones, cloud computing, and more devices than I could ever have imagined needing to be charged.

In 1982, EPCOT Center opened at Walt Disney World, offering an entire collection of exhibits devoted to imagining tomorrow. I loved the idea that people were building physical places where you could experience the technology of a future time. Of course, the future has an interesting habit of refusing to arrive exactly as advertised. We still don't have flying cars parked in every driveway. But I can make a video call from an airplane, carry thousands of songs in my pocket, and ask a small device on my desk questions that once would have required a trip to the library.

Somewhere along the way, what was once science fiction began turning into ordinary life.

Kirk had been the captain of my childhood imagination — action, adventure, exploring the unknown, winning the fight, and often the girl’s affection. By the time Patrick Stewart took the center seat as Jean-Luc Picard, I was older too. Picard was different. He thought before he fired. He listened. He questioned. He faced the Borg. The future was still full of impossible technology, but the stories had become more interested in what humans might do with it. And then there was Data as an android that could reason, learn, communicate, and would spend years trying to understand what it meant to be human. Somewhere along the way, I had changed too.

The questions became considerably larger than whether a computer could add numbers faster than I could. What is intelligence? What is understanding? What separates information from experience? What is the difference between observation and evaluation? Now I was learning lessons on emotions, love and life, but no longer as a 6-year-old dreamer with my head in the clouds reading in the basement or watching a TV show. As a young adult the events I used to dream about were becoming real and would take me to places that not enough people are able to experience firsthand.

I have since helped introduce new sound systems, built technical infrastructure, worked with early digital technologies, started businesses, managed productions, and developed relationships with people whose jobs depended on making complicated things work. I'd learned something important along the way. The technology itself was rarely the problem. It was more often the change. People often had to be given a reason to change something that they were accustomed to.

Sometimes I was the person introducing the change. Sometimes I was the person who had to accept it. Sometimes I had to work alongside a person who was completely resistant to changes they didn’t understand. By late 2025, I had nearly fifty years of experience watching the future become the present, and I've spent decades in the live-event industry, watching technology change almost every aspect of how we create our experiences.

Ray Kurzweil and others began writing seriously about the possibility of a technological singularity, a future in which accelerating machine intelligence could transform civilization in ways that would be difficult to predict with certainty. Whether or not those predictions prove accurate, the questions were no longer confined to science fiction. Now artificial intelligence has begun making another leap into everyday life. This time, there wasn't necessarily a new mixing console to learn, a computer language to master, or an elaborate technical system to configure before I could begin… I'd seen enough change to recognize when something deserved my attention.

This new technology could respond, ask questions, help organize ideas, and participate in work that previously required an entire collection of separate tools and applications. Was this really a new form of intelligence? Was it understanding what I was saying? Was it the beginning of something Kurzweil had been describing for years? Or was it just an idea that started as a tv show about the future or a great science fiction novel? I didn't know. What would I say to Data if I met him today? Could we have a conversation about living life?

The light in the tunnel wasn't coming at me. It was already here.

So I subscribed to ChatGPT.

I wasn't looking to reinvent my life overnight. I wanted to understand what was happening, what was possible, and how it might affect the things I already knew how to do. After all those years imagining the future, this caught my attention as a big deal. All the years learning technology didn’t really change what I did, and I had found the Girl, but I did have a few things I wanted to improve.

It Started with Tomorrow Morning

In November 2025, I decided to make a few improvements.

Nothing particularly revolutionary. I wanted to organize my professional life, improve my online presence, clean up an email inbox that had accumulated far too much history, and develop some more consistent daily routines. It did not yet feel like something that required me to change, but it was exciting to imagine the possibilities of a technology I did not yet understand. I wanted to learn more about what artificial intelligence was. Not necessarily to become a programmer or suddenly reinvent my entire career. I was simply curious about what these new tools could do, and more importantly, how I might incorporate them into my day-to-day life.

I had been freelancing in the live-event industry for nearly forty years. During that time, I'd accumulated thousands of photographs, countless professional relationships, stories, accomplishments, a few disappointments, and more than enough experience to fill a resume. Finding a way to present the story in a useful way was another matter. Friends told me I should write a book, and although I did want to pass on lessons I had learned, I was not sure if anyone wanted to learn them outside of the lobby bar.

So, I quickly became we and together we established something called the Improvement Plan.

The first agenda was almost comically ordinary. Wake up. Have coffee. Check email. Spend a couple of focused hours improving something. But keep a record of what happened. Two hours in the morning, maybe one less video game, maybe one less tap on the snooze button. That seemed like a reasonable place to start.

The Digital Legal Pad

I've been using Apple's Notes application for a long time. In fact, the oldest note I could find dates to 2012. It contains a few numbers from a tour, including mileage between a hotel and a house. Nothing profound. Just information I needed to remember. For years, Notes served that purpose. A place to jot things down, capture a thought, save a telephone number, or record something that might become useful later.

I understood how to take notes. That wasn't the new part. I had a day timer or a legal pad next to me most of the time. The Franklin Covey store was as much fun as Best Buy. What changed was how I began using them while working with ChatGPT. Instead of treating a conversation as something that happened and then disappeared into a chat history, I started using Notes as a digital legal pad alongside the conversation. A place to capture ideas, organize objectives, collect the things we wanted to revisit, and keep useful information accessible outside the chat. That distinction might seem minor, but it changed the workflow. I could now think out loud with an assistant, capture something worth preserving, and return to it later. The notes provided continuity. The conversations helped organize and develop what I was thinking. It was no longer just a giant collection of multicolored Post-It notes on the wall.

We began experimenting with Apple Shortcuts to make that process easier. One early shortcut turned a repetitive note-taking task into something much faster. Another attempted to merge daily notes into a single summary. And that's where the first little complications appeared. The Shortcuts interface didn't always behave as expected. Variables appeared in unexpected places. Controls weren't always available where the instructions suggested they would be. Sometimes the process required starting over with a cleaner approach.

It was frustrating at times, but it was also instructive. We weren't just learning how to operate a single application. We were learning how to communicate. We shared what was happening on the screen, recognized assumptions from two different perspectives each with its own user interface, adjusted our approach, and tried again. The first change-agent experiment with this new intelligence was happening in real time, right in front of us.

Building the Cockpit

I've spent much of my career sitting behind control surfaces. Audio consoles, computer systems, communication networks, and production desks all serve a similar purpose. They put the right information and controls within reach of the person responsible for making something happen. The system can be extraordinarily complicated behind the scenes, but the operator needs a useful way to interact with it.

I began thinking about my home workspace in much the same way. My new M2 Mac mini would become the primary workstation. The MacBook, iPad, and iPhone would serve different purposes depending on where I was working and what I needed to accomplish. We explored the known tasks like Notes, email management, Microsoft Office, Dropbox, Adobe applications, browsers, and the tools I'd already been using in live production.

Anyone who has built a live-event system knows there's a period when the equipment is technically present, but the system isn't quite ready to operate. Cables are connected. Network addresses are being identified. Signals are being tested. Gaps are discovered. Something else needs a firmware update. Eventually, things begin talking to one another… eventually.

The same thing was happening here. There were new applications to install, accounts to configure, files to organize, and devices to synchronize. At one point, I was using the MacBook to document the process while the Mac mini was downloading an update. We learned when the keyboard was taking too much time, and when one emoji on the iPad said enough. We discovered talk to text while taking my dog for a walk.

We started calling the workspace the digital cockpit. It wasn't a particularly sophisticated invention. It was a practical attempt to create an environment where I could spend less time finding things and more time doing something useful with them. But the act of building it raised another question. What exactly was I building it for?

A Little More Than a Resume

One of the original objectives of the improvement plan was to improve my LinkedIn presence. That meant updating my profile, organizing professional recommendations, and finding a better way to describe what I actually do professionally. I've worked as an audio engineer, production manager, technical director, systems engineer, and in plenty of roles that don't fit neatly into a single job title. For years, much of that work came through relationships. Someone knew me. Someone had worked with me. Someone needed a particular combination of technical experience, judgment, and the ability to stay calm when things weren't going according to plan.

The telephone would still ring, but I was starting to feel behind. I started to feel like I did not know how to communicate who I was to an AI recruiter. It seemed like there must be a new way to network in this Language Age. How to share my skills and core competencies with someone who had never worked with me was becoming a different challenge.

We began looking through photographs from my career. There were thousands. Unfortunately, thousands of photographs aren't much use when you can't find the twenty you need. So, we spent time learning how to sort, export, transfer, and organize images across devices. Tasks that sound simple when written on a checklist can consume an entire afternoon when the files are scattered across years of different storage systems.

Then came an idea for a LinkedIn post. I had photographs showing something every event professional recognizes: cables. Messy cables. Organized cables. Cable ramps protecting the paths people need to walk. We assembled four images into a progression from chaos toward something more organized, protected, and ready to use. It was a simple visual story. But it also happened to illustrate something I had spent most of my career doing. Taking complicated situations and making them manageable.

On November 16, we published the first carousel. The first version wasn't a masterpiece. We tried editing images, considered different approaches, and eventually decided the original photographs told the story well enough. We had taken an experience from the physical world, organized it into a sequence, added context, and communicated an idea to people who weren't standing next to me. And we had done it through a new kind of collaboration.

I began to see possibilities beyond simply improving a résumé.

Putting a Face on the Work

A website seemed like the next logical step.

We began exploring Squarespace, looking at templates, gathering more photographs, and deciding what someone should encounter when arriving at the site. There was a hero image to choose, a headline to write, services to describe, and a career that needed to make sense without requiring someone to read forty years of history.

That was harder than I expected.

I knew how to introduce a live event. I've been involved in thousands of them. The opening moments matter. Before anyone speaks, the room has already begun communicating. Lighting, sound, scenery, timing, and the energy of the audience all contribute to that first impression.

A website has an opening moment too.

We started working on mine. The headline changed. The photographs changed. The descriptions changed as I realized that certain words made my experience sound narrower than it was. I wasn't simply presenting myself as an audio engineer looking for the next show. I was trying to communicate the larger collection of skills that had developed around that work.

We began discussing experience, leadership, systems, innovation, and the possibility that AI could become another useful component of an already complicated professional life. And, as expected, the software had opinions of its own. Controls moved. Instructions didn't always match the screen. Some visual changes affected elements we hadn't intended to change.

We even discovered that we'd been building on a Squarespace trial site rather than the site on the domain we wanted to use. That was an expensive lesson in time, although not necessarily in money. We had to reconstruct work we'd already done. There were moments when six hours of effort seemed to have produced considerably less than six hours of progress.

But there was a difference between repeating the work and repeating the learning. Once we understood the account structure, the layout, and some of the interface behavior, we could approach the rebuild with more confidence. We were beginning to learn something about the relationship between capability and usability. Just because the tool can accomplish something doesn't mean the path to accomplishing it will be obvious.

And just because an AI assistant can describe a procedure doesn't mean it can see the same interface the human is looking at. We needed screenshots, questions, corrections, and sometimes a completely different approach. Life with AI was becoming a team sport.

The Binder

While all of this was happening, another part of the project was growing. The binder. I've used production binders throughout my career. They contain the information needed to bring an event together: schedules, technical details, plans, references, decisions, and the many other things people need to know before something goes wrong.

So, it seemed natural to create one for the Improvement Plan. We began organizing daily logs, website notes, AI experiments, reference materials, images, and ideas worth developing later. Some documents were practical guides. Others were reflections. A few contained stories that had very little to do with building a website, at least on the surface. We even started documenting the differences between AI models and thinking about which tools were useful for which kinds of work.

The binder was becoming a record of what we'd tried, what had worked, what hadn't, and what we might want to do differently next time. It was an organized collection of notes with a timestamp. And an important distinction was emerging. I didn't need to master every new application. I needed to understand how to get useful work done. That meant learning when to use a tool, when to change tools, when to ask for help, and when the most productive thing I could do was simply stop adjusting something that already worked.

For someone who has spent a career solving technical problems, knowing when to stop is an important skill.

The View from the First Hill

By the middle of November, we'd made real progress. My daily routine had more structure. Notes had become a working companion to our conversations. Shortcuts were reducing some repetitive tasks. The digital cockpit was taking shape. We had improved LinkedIn, published a visual story, established the beginnings of a website, and created a binder to preserve what we were learning. There were still plenty of unfinished tasks.

Files remained scattered. Some applications weren't configured. The website was incomplete. The binder needed organization. We had more photographs than we could reasonably review and more ideas than we could develop at once.

But we had accomplished something useful. We'd established a way to work. Looking back, I recognize the experience from countless live-event setups. Early in a production, there's a moment when enough of the system finally comes together that the team can stop concentrating exclusively on getting the equipment operational, and you can start building a show, the show, a live event. That doesn't mean the work is finished. It means the creative work can really begin. Our modest Improvement Plan had brought us to that point.

We'd climbed the first hill. And for the first time, we could see how much farther the landscape extended. There was a website to finish. A professional story to tell. Decades of experience to organize. New technologies to understand. New relationships to develop. Possibilities I hadn't seriously considered when I first sat down with a cup of coffee and a two-hour agenda.

What started as a few improvements to tomorrow morning was becoming something considerably larger. We needed a plan. We gave ourselves six weeks.

And suddenly, that first hill looked pretty small.

Read More
James Jorgensen James Jorgensen

Field Note 04 — I’ll Meet You…

Notes from the Lobby Bar

“I'll meet you…”

I've probably said those three words over a thousand times in the last forty or so years. I'll meet you in the lobby. Let's grab coffee before heading to the ballroom. Lunch? Meet me downstairs in 15 min after I drop my bags. Sometimes there's an agenda, but often there is not. The request may be a desire to simply vent after a long day. Sometimes it might simply be the unspoken thought when I look through a window and see who is already in the room. The destination isn't necessarily important. It's the opportunity to spend time together, talk, share ideas, or perhaps work through something that needs a change in scenery.

I've spent most of my professional life alongside brilliant engineers, producers, technicians, artists, executives, and more than a few pirates. Live production is an industry where people from remarkably different backgrounds come together, accomplish something extraordinary under considerable pressure, and then scatter in different directions.

I’ve also lived an extraordinary life where that same experience came from a wedding, or the birth of a child, or the doctor’s office. The anticipation of meeting somewhere has evolved over the years, but waiting for an Uber is not much different than standing in the snow waiting for the school bus to arrive. Many of my memories involve meeting what’s next.

Let's Go for a Drive

Years ago, I had a couple of employees that didn’t get along. They would often loudly disagree on the littlest thing. It got to the point where they would vent to peers and try to convince them to take a side. It was escalating to a point where a manager needed to act.

I could have scheduled a meeting or sent the situation to the HR department. Most frequently I would try to directly mediate the situation and simply tell them to knock it off. I would often say to someone, “Let’s take a walk,” and then explain my expectations with various results.

Instead, this time I scheduled a different type of meeting and put them together in the cab of a truck for a six-hour drive across the desert.

Six hours.

No conference table. No formal agenda. No manager directing the discussion. Just two people, a truck, and a considerable amount of highway. It worked remarkably well, and they are still friends to this day. The lesson wasn't that everyone should resolve disagreements by driving across the desert. It was that changing the circumstances of a conversation can sometimes change the conversation itself.

I've sometimes wondered whether there was a sophisticated management term for what I'd done. Perhaps Interactive Human Resource Management. I.H.R.M. I just thought they needed some time together without trying to show off to peers. They really needed to “meet.”

And that observation stayed with me.

Meet Me in the Lobby Bar

Anyone who's spent much time traveling for work probably understands the significance of a hotel lobby bar. For those of us in live events, it's almost an extension of the workplace. Food, a beer, an Old Fashioned with great bourbon, or maybe simply some water to hydrate and some wasabi peas.

The day is over. The external obligation is finally beginning to subside. Someone says, “Meet me in the lobby bar.” And people arrive. Sometimes it's the same group you spent the previous fourteen hours working alongside. Sometimes somebody brings a friend. Occasionally, someone you've known for years happens to be staying at the same hotel.

There's no seating chart. Conversations start, stop, overlap, and wander. World problems become topics. Somebody remembers a show from twenty years ago. Somebody else has a problem they're trying to solve. A friend may reveal a worrisome health issue or announce a new romance as gossip. It may include some epic war story about Pakistan or an event that Han Solo would remember. It could just be a story about shoes.

Before long, an informal gathering becomes an exchange of experience that no meeting organizer could have planned or placed a value on. Not every conversation is profound. Some are downright ridiculous. But over the years, I've watched remarkable things happen in those rooms and have become aware of the diversity of people that experience them.

Problems get solved. Relationships develop. Opportunities appear. People discover they have more in common than they realized. And occasionally, somebody picks up the tab.

Then everyone leaves, and what happened in the moment becomes a memory.

What Did We Eat?

Not long ago, I invited a close friend, Tony Pitsley, to join an experiment I was conducting. I wanted to recreate something resembling those familiar lobby bar conversations, but in a digital environment.

He and I have many shared memories from having to explain the value of $200 to each other, the exhaustion from too many late-night drives, and the excitement of some new technology. He is “Uncle Tony” to my kids, and I was the best man in his wedding.

Tony didn't join. He called me instead. He wanted to know what I was up to with this one. He has known me for a long time. I asked him a question: “Remember that old tobacco factory restaurant we ate at years ago?” Of course he remembered. He replied, “That place was awesome,” and I asked, “Do you remember what we ate?” He did not, but neither did I. We both remembered the experience, but not the details. That once again got us talking about all the places we'd been, the people we'd met, and the many conversations we'd had over the years.

How many problems have we all solved over a dinner? How many ideas have been exchanged in hotel lobbies? How many times has somebody said something that changed the way another person approached their work? And how much of that collective experience has simply disappeared into memory?

What if it didn’t have to?

What if we could return to an earlier conversation, remember what had been discussed, and continue to develop an idea with everything that had been discussed, including the surrounding context?

Not to record every word somebody said over a cocktail. Certainly not to turn a night with friends into a business meeting. But to preserve useful experiences and make them available again when they mattered. Some of those meetings could have become TED Talks, and yes, some did not produce anything but a “Hey, I had a good time last night, thanks.”

That was the idea behind the experiment.

I started inviting people into a shared conversation environment. Some understood immediately. Some were curious. Some were skeptical. And some, like Tony, picked up the phone. Which, when I think about it, was perfectly appropriate. The objective was never to get everybody using a particular application. It was to get people to think about all the lost context and together find a way to retain it with minimal effort or obligation.

Who's the Bartender?

Once I began experimenting with a shared digital conversation, another question emerged.

If the lobby bar was the setting, who was taking care of the room? I didn’t want it to be about me. In a real lobby bar, a good bartender does considerably more than pour drinks. They recognize the regulars. They remember preferences. They may introduce two people who ought to know each other. They notice when somebody wants to talk and when somebody would rather be left alone. And a particularly good bartender understands discretion.

So, I began exploring whether an AI participant could assume some of those responsibilities. Not as the star of the conversation. I did not want to build an AI bar that acted as an authority telling everyone what to think.

As the bartender.

We experimented with group conversations involving people I'd known for years. I invited friends and colleagues into the experience, each bringing different expectations and their own ways of interacting with AI. At one point, I even asked the AI to explain its role as bartender to Tanner, one of the people participating.

We weren't simply asking a chatbot to answer questions anymore. We were exploring how an AI might participate in a conversation among people who already had relationships, history, and shared experiences, but from different perspectives. The environment should support the conversation, not become the reason for it.

Could it recognize a connection between two conversations? Would it retrieve something useful that we'd discussed earlier? Could it introduce context without intruding? Is it even possible to understand that sometimes the best thing a bartender can do is keep quiet? We have two ears and one mouth by design, and I did not fully understand how AI could participate.

We hadn't built a complete system that could reliably perform all those functions. But we'd developed a surprisingly clear idea of what we wanted that system to accomplish. We wanted a greeter to welcome someone into the conversation. We wanted a barista who remembered how you liked your coffee. We wanted a very intelligent archivist with a great memory that could help recover earlier discussions in detail, without the foggy headache of trying to remember them ourselves.

As we invested more time in a group text chat, we began imagining the other roles that were evolving, and the unexpected happened. The conversations inside the chat led to other discoveries outside of the room. Some were personal and self-reflective; other conversations led to construction projects, and some led to revenue opportunities.

The important part wasn't that we were trying to build an agent. It was validating the experience of the people who came to meet.

One More Thing…

I didn't invent the value of meeting or spending time together, sharing those experiences, and learning from other people. Those things have been part of my life for decades. What changed was the possibility that we might preserve some of what happens when we meet and allow more people to benefit from those experiences.

My thought at the time was that we could introduce a new participant who could help. It was an intriguing idea. It also raised a question: How?

Which seems like a good reason to meet again.

Could we build this thing?

Read More
James Jorgensen James Jorgensen

Field Note #3 — Exciting, but Bumpy

Working Draft V3.0 | October 12, 2026

Where did we start?

A friend asked ChatGPT if I was a good guy to know. The reply was interesting in that he got the affirmation he was looking for, but I suddenly wanted to improve my online presence. I wanted to update social media, build a better website that represented the range of work I had done and told a story, and I wanted the new generation to better understand the direction I wanted to go professionally. I had decades of experience in live events, photographs, stories, and a solid black book network, but had very few ideas about how to incorporate AI into my day to day.

The technology was fascinating. I could describe something I wanted to create, via text, and my new assistant could help me explore the possibilities. We could discuss ideas, try different approaches, and find ways to communicate things I had previously struggled to put into words.

But eventually, we had to decide where to begin improving my online presence. A website seemed like a reasonable place since I had populated a Flash template before, and that seemed like it would be easy. A cool website that could showcase my story and be interactive enough for other people to enjoy.

That part was exciting.

It’s not where we started

I wanted to keep notes as we went, not because I anticipated writing about artificial intelligence someday, but because there was a lot to learn, and I didn't want to keep learning the same things twice. There were conversations, instructions, screenshots, links, and explanations. Sometimes we made enough progress that I wanted to preserve it before moving on. I learned to use Apple Notes, saved PDFs, and started collecting documents on several devices.

However, even the process of saving a screenshot was new and not natural. I had snipped in Windows but did not know how to save a screenshot on a Mac. Some of those notes were simple thoughts. Others were about learning how to work with the assistant itself. I was trying to remember what we'd done yesterday so we could accomplish something today. Looking back through those early notes, I can see the pieces accumulating.

We tried to replicate simple workflows that I had used for years, but with new tools. I remember building shortcuts and attempting to automate my day. The technology was new and exciting, but communicating through some of those first steps proved surprisingly difficult. My assistant would tell me to find a control, select a block, or change a setting. Except sometimes the control wasn't where the instructions said it would be. Sometimes it wasn't visible at all.

That's not on my screen

More than once, I wished my new assistant could simply look over my shoulder and see my screen.

What could it see? What was it assuming? Did it understand the interface I was using, or was it describing another version? What did I need to show it before its instructions would become useful? How could it know every detail of a new piece of software when there was no manual yet to read? I did not know what a prompt was or how to code. It was an interesting time learning what a sidebar was and how much information could be hidden behind three little dots.

A change that appeared to apply to one element might affect something larger. The help files, user guides, and the interface in front of me didn't always agree with the instructions I was being given. My assistant could explain things, but it didn't always understand what was happening, and my assistant could sound very certain about a screen it couldn't actually see.

I could understand the desired result and still be unable to find the next step. I knew what we wanted to accomplish, but I was learning how to operate new tools, and just keeping current versions of software became a daily task.

My experience in live events was becoming more visible. My background had taught me that producing ideas and putting them into practice were two very different efforts. I've spent much of my working life learning systems, tracing signal paths, and helping other people operate unfamiliar equipment. Here I was, struggling to make a simple visual change on a computer screen.

And there was another part to learn, too. How to speak the same language as my assistant.

Learning to communicate

We got going with the idea of Online Presence continuing as our north star, but sometimes the navigation required different approaches. Sometimes a different browser, sometimes a different model of AI. We kept at it, next thing next. I would post screenshots and save Notes often. We built saved summaries and guides as PDFs. We maintained the conversation throughout the process, and the things we were trying to build were quickly evaluated and then either kept or discarded. We did not stop. We had to learn a balance between pausing and running full speed.

Sometimes we found the right control. Sometimes we changed the design to fit what we could make work. Sometimes we accepted a version that was good enough for that day. We often compromised more than I expected or wanted to, but toe by toe, the elephant got smaller. The wording could be right while the layout was wrong. The image could work while the button didn't. We could have a complete plan in the conversation and still have an incomplete page on the screen. Questions emerged through the process. We didn’t always start in agreement.

The conversations weren't just producing questions anymore. They were becoming part of the process of getting things done. I was learning when to ask a question, when to share a screenshot, when to challenge an instruction, and when to stop trying to solve something through conversation alone. There were still misunderstandings, repeated steps, and things that didn't work the way we expected.

Not perfectly, but we were making real progress.

On November 14, I saved a reflection about finding traction: moving onto the Mac mini, syncing cleanly, refining the post, and feeling the system—and the process—begin to align.

A few days later, we were still getting tangled in website controls, but we were communicating about them.

Something tangible… a website?

Eventually, some of the smaller accomplishments began to matter as much as the larger ones. In live events, I've always understood the importance of an opening. Before anyone says much, the room has already communicated something. A website had to do that too.

So we started with a Hero section.

We tried headlines, paragraphs, photographs, and different ways of describing what I do. I corrected language that made my experience sound narrower than it was. My assistant offered alternatives. I chose, adjusted, and tried again. More context often changed the mutual perspective.

We built a footer. Made the Home and Contact links work. Learned that a button could behave differently outside edit mode. Those were practical discoveries and felt like progress. They gave me something I could test instead of another explanation to follow. The Coachella stage image became part of the opening. We worked on its crop, cleaned up distractions, and adjusted the text around it.

I also stepped back to pen and paper.

I knew how to sketch movement, structure, and what should happen next. Bringing that familiar method into the process helped me find my bearings. The new tools were becoming part of my workflow. I was still working out which task was best served by which tool, and which version of the tool was best. Much like when moving from analog to digital, my workflow was established, and we found the right combinations.

Learning while building

Looking back, I can see that we were building two things at once. A website and a way of working together. As we improved the context, communications became easier. At the time, I was mostly trying to get the next thing done. I wanted help expressing my experience, and I wanted to learn new tools without spending the whole day fighting them. I wanted my assistant's guidance to connect with what was in front of me. There were also times when I wanted my assistant to just do the work, but frequently learned something unexpected by collaborating.

That connection took work from both sides of the conversation. I had to provide context, question assumptions, and say when something didn't make sense. The guidance had to change when the screen contradicted it. I began to feel the difference between just getting an answer to a prompt and finding solutions together. We still have a lot to do on the website.

It is exciting.

It is bumpy.

Read More
James Jorgensen James Jorgensen

Field Note 02 — I Kept the Notes

I kept the notes.

That matters, because I don’t have to remember how this started or polish the beginning into something smarter than it was. I can look.

There’s a joke about the second record. Chickenfoot skipped the problem and called theirs Chickenfoot III. I worked those shows, so I appreciate the joke more than most. I’m not going to try to make Field Note 02 bigger than the first one. I’d rather leave some of the room noise in it.

It started with a pretty ordinary request:

Help me improve my online presence.

That was it. I wasn’t trying to learn AI, looking for an agent, or thinking about context containers, useful outcomes, or whatever we might someday call the next era of computing. I wanted some help cleaning up LinkedIn.

What came back was a six-week Improvement Plan. Week One was Foundation & Visibility: LinkedIn, workflow rhythm, morning routine. Week Two was email and workflow. Week Three was visual identity. Week Four was Apple Notes and Shortcuts. “AI in Action” didn’t even appear as a formal theme until Week Five.

That detail matters now.

AI wasn’t the project. My life and work were the project.

Fortunately, I kept the notes, so I don’t have to reconstruct those first few days from memory.

November 9, 2025

The agenda was pretty ordinary: coffee, email, LinkedIn, SaneBox, and keeping track of what I did. I was already using AI to help summarize the day, suggest what might be automated next, and notice whether all this “productivity” was actually improving the balance of my life.

By the end of that first day, something had already gotten my attention. A process that had taken about 75 minutes took 30 seconds. The same note records why that mattered: productivity, creativity, and time with my wife.

I didn’t have a theory for it. It was just useful.

November 10

The work was still mostly about improving what I already had: LinkedIn, references, SaneBox, Apple Shortcuts, workflow. One of the notes simply said to watch for new AI ideas or automation opportunities during the day. AI still wasn’t the destination.

That evening’s reflection included this:

“The time invested in learning and setup will free future time for creativity and family.”

Again, no grand theory. Just time.

November 11

This is where the notes start getting more interesting.

I had begun cleaning up an absurd email backlog. SaneBox had taken the unread count from roughly 100,000 to under 70,000, and I had started tracking time, costs, and subscriptions.

Then, right in the middle of the Daily Tasks note, I wrote:

“I’m paranoid- afraid of the new, and click bots.”

That sounds like me. Not today. Then.

I was curious and resistant at the same time. In hindsight, that isn’t unusual for me. I approached a lot of technological changes that way — analog to digital, the internet, cell phones. Interest first, resistance right beside it, then eventually a practical question:

Does this make my life better?

I don’t need to turn that into a résumé of every transition I’ve lived through. The point is simpler: resistance was part of the pattern, not evidence that the change wasn’t real.

November 12

Then we tried to build something.

The goal was simple: create an Apple Shortcut that would take selected Notes, merge them into one document, ask for a title, save it in the Improvement Plan folder, and open it automatically.

It did not go smoothly. The Mac and iPad behaved differently, controls that were supposed to appear didn’t, actions changed themselves, inputs got substituted, and eventually the editor became sluggish enough that we were restarting things and trying again.

The result wasn’t magic. We ended the day with a working draft, a better understanding of the system, documentation of what had failed, and a clear path for the next attempt.

The objective for November 13 was almost boring: start clean, rebuild it, test the working version manually, and only attempt the more ambitious automation if the system stayed stable.

That feels familiar. It is pretty much how I have approached new technology for most of my career: learn enough to make it work, find out where it breaks, and keep going.

By then I had also started sorting the notes themselves into categories: Daily Logs, Reflections, Tips and Fixes, Creative ideas, and Meta observations. Some were intended for daily records, some for an Improvement Plan, and some might eventually become chapter material.

I didn’t know I was building an archive. I was just keeping notes.

Almost a year later, that turns out to matter.

Because I don’t have to polish the beginning into something smarter than it was. I don’t have to pretend I understood where this was going. I don’t even have to pretend I liked all of it.

The record is there.

The story did not begin with a theory about artificial intelligence. It began with:

Help me improve my online presence.

Then something happened in the interaction. The work got bigger. The conversation got better.

And fortunately, I kept the notes.

Read More
James Jorgensen James Jorgensen

Field Note 01 — Where do I start?

I kept looking for the first encounter. Now I am looking at the first shared effort: organizing a day, making a plan, and giving the work a place outside the conversation.

FIELD NOTES FROM THE LANGUAGE AGE

Day One · September 29, 2026 · Jim Jorgensen

Observation

I kept going back further in time, looking for the right beginning. There has always been something to better understand, experience, and learn from. Simply stacking speakers different ways in order to achieve different results. Using road cases with wheels. Then came the PC, AOL, and cellular phones that would fit in my pocket. Audio moved from analog to digital. Using a PalmPilot device to take notes instead of a legal pad seemed so advanced. Tech companies like Google and Microsoft were once new. Online commerce impacted the retail experience—I can remember going to a shopping mall just to hang out with friends.

I have been witness to many changes, always with the wide-eyed excitement of discovery. Finding the next LEGO piece is an important part of the experience.

But the beginning of this particular new adventure now looks and feels like something bigger. On November 9, 2025, I asked ChatGPT to help me organize my day…

Context

I came to this through work: live events, pre-production, and the practical business of getting people and systems ready for what happens next. An outdated online presence and difficulty finding work were part of the environment. I was trying to find a useful place to start building new habits and a better work/life balance.

Stocking shelves in an emergency room, writing a field note, packing a suitcase, building a P&L statement, and setting up a live event seem like different activities. Looking back, I can see a thread running through all of them: What do I have? What do I need? And where does it go?

Field evidence

I have had a longstanding habit of thinking a lot, and sometimes I would talk about it, but more often the thoughts would just fade away as the next thought would start to take shape.

Sometimes I would jot down a thought somewhere, but I identify January 29, 2012, as the start of saving my thoughts as notes—be it a grocery list or an epiphany of some sort. November 9, 2025, was the day I had too many random notes and asked for help organizing my day.

In looking for a starting point, I also revisited the first saved PDF in my binder: a six-week improvement plan that took what I had and what I needed out of my head and turned those thoughts into tasks that I could act on.

These dates and that artifact are starting points for this account; the experience of learning and collaborating with another intelligence over the past year is what these posts will be about.

What changed for me

That particular document matters to me because we made something together—it was more than a PDF. It was tactile collaboration where I could dump ideas, thoughts, and worries and receive a guide to act on them. It gave the seemingly random talking points a place to exist outside of conversation. Simply organizing one day gave us an immediate purpose. Making a plan gave that purpose a form. Now that plan can produce tasks that gain traction as they are implemented.

I now think of the PDF as an early context container: a bounded place to hold the work. The document held relevant information. What happened around it—using it, returning to it, deciding what came next—made it useful. Before this, it seemed like I was often cleaning off my desk only by putting items in an inbox until it was full and eventually dumping that inbox into a letter box and stacking those letter boxes in the back corner of my office. Now I start with an executable plan. I can see a path from the thought to the task and enjoy crossing items off the list when they’re complete.

Why I think it matters

“Where do I start?” may be a more productive question than trying to absorb everything a new technology can do, especially at today’s pace. Observing the situation before starting the next task gives us something to evaluate. Evaluating what happened helps me notice friction or failure and make a better decision about the next step.

That is the purpose of these Field Notes: to record observations from living systems where humans, technology, context, and intelligence meet. The explanations can change as the evidence grows and solutions become evident.

Open edge/Next

What makes a shared plan become executable? When does a document help the work move, and when does it simply become another thing to maintain? How is this different from all the other changes in technology I’ve experienced over the past 50 years? Is it better?

Threads to follow: Context containers · Observation and Evaluation · Gauges · Definitions for some old words like Thought, Latency, and Language…

Read More