LinkedIn works when you show up consistently. The problem is it takes forever. From finding ideas, to writing posts, engaging with people, and figuring out what's actually working…

Taplio handles all of it in one place.

Creators have used Taplio to grow 30,000+ followers. 

Sales teams have generated $3M+ in pipeline.

All just from LinkedIn.

Try Taplio free for 7 days and get your first month for $1 with code BEEHIIV1X1.

Try Taplio for free.

Every Sunday I write down three things the week actually taught me. Not ideas I had confirmed. Not content I consumed that sounded smart. Actual lessons, the kind that came from doing the work, running into the wall, or noticing something in real time that I hadn't noticed before.

The rule I hold myself to is this: if I could have learned it from a book without living it this week, it doesn't count. These have to be earned lessons, not borrowed ones. Here is what this particular week delivered.

1. The System You Don't Document Doesn't Exist

I spent approximately ninety minutes on Wednesday trying to recreate a workflow I built about three months ago. A Make.com automation that handled a specific type of client onboarding sequence, sequencing emails, populating a CRM, triggering a Slack notification at the right stage of the process. I needed to adapt it for a new client situation and I could not, for the life of me, reconstruct what I had originally built because I had never written it down.

I had the vague outline of it in my head. I remembered the general logic. But the specifics: the exact module sequence, the conditional filters, the field mappings, the edge case handling I had added in iteration two, were gone. Vapor. Three months of operational distance had taken the detail and replaced it with a fuzzy approximation that was close enough to feel familiar but not close enough to be useful.

I got it working eventually. It took me three times longer than it should have and I was genuinely irritated at past-Dan the entire time in a way that felt both justified and slightly absurd given that past-Dan was me.

The lesson that landed, and I mean landed in the way that something lands when you have lost ninety minutes to your own laziness: a system that exists only in your head is a single point of failure. It is not a system. It is a habit that has been cosplaying as a system, and habits are personal and fragile and non-transferable. Systems are documented, repeatable, and verifiable. The difference between the two is not technical sophistication. It is whether you wrote it down.

There is a version of this lesson that is easy to nod at and immediately forget because it sounds like productivity advice you have heard before. But the feeling of sitting in front of a blank Make.com canvas trying to reverse-engineer your own previous work is a specific kind of frustration that makes the lesson stick in a way the abstract version does not. So I am sharing it in its full inglorious detail in hopes that you can learn it without losing the ninety minutes.

What I did immediately after getting the workflow rebuilt: I wrote it down. Every module. Every filter. Every conditional. Every decision point. I now have a running workflow log that I update every Friday as part of my end-of-week review. It is not exciting work. It takes about twenty minutes. It will save me hours of reconstructive archaeology every time I need to revisit or adapt something I have already built.

Document the system or the system doesn't exist. That is the lesson. I am not sure there is more to say.

2. Constraint Is a Creative Accelerant

This week was tighter than usual in terms of working hours. The Orlando settle-in process has a long administrative tail that nobody really warns you about: appointments, deliveries, utility registrations, the various bureaucratic small print of establishing yourself somewhere new. Several chunks of time I had planned to work were not available to work, and I went into the week with a realistic expectation of getting less done.

What actually happened was the opposite. I had one of my most creatively productive weeks in recent memory. The Tuesday Tactics piece came together faster than almost anything I have written in the past six months. Decisions that I might have deliberated on for an hour got made in ten minutes. The work that happened, happened with a focus and directness that I rarely hit in weeks when I have more time to fill.

I have known about Parkinson's Law for years. The idea that work expands to fill the time you give it is not new information. But knowing something as an intellectual concept and feeling it operate in your own nervous system in real time are genuinely different experiences, and this week reminded me that the gap between the two is wider than I usually account for.

When I have all day to write something, I spend the first hour and a half doing things adjacent to writing. I research. I outline. I reorganize the outline. I think about the angle. I make coffee. I come back. I write a paragraph and decide it is wrong and start again. The writing eventually happens, but it happens after a significant amount of what I can only describe as warming up the engine while already sitting at the destination.

When I have two hours to write something and there is a hard stop at the end of those two hours, I open the document and I write. The absence of an option creates the presence of focus. The constraint is not a problem to work around. It is a feature I have been accidentally engineering out of my better weeks by giving myself too much room.

The practical implication I am taking from this is something I want to experiment with deliberately over the next month. I am going to start giving myself internal deadlines that are significantly tighter than the actual external deadlines I am working against. Not fake urgency as a performance trick, but genuine time-boxing that forces the kind of focused output I saw this week. If I need to write something by Friday, I am going to tell myself it is due Wednesday and see what that does to the quality and speed of the work.

Constraint is not the enemy of creativity. For certain kinds of work and certain kinds of personalities, it might be the primary fuel. I want to test that more intentionally instead of just experiencing it accidentally when life gets busy.

3. Buyers Don't Want Perfection. They Want Certainty.

I had a sales conversation this week with a prospect for Pinnacle Masters, my consulting practice. The call ended with a yes, which was good. But what I keep thinking about is not the outcome. It is the specific moment in the conversation where I could feel the shift happen, where the dynamic changed from exploratory to decided, and why it happened when it did.

I had prepared thoroughly for this call. I had the methodology mapped out. I had relevant case studies ready. I had a clear articulation of the framework we use and the outcomes clients typically see and the specific ways we approach the kind of problem this prospect was dealing with. I was ready to be impressive in the way that a well-prepared consultant is impressive, with the depth and rigor that signals expertise.

None of that is what closed it.

What closed it was a moment about twelve minutes into the conversation where I stopped presenting and just told them directly what I saw. Here is the actual problem. Here is why what you have been doing about it has not worked. Here is exactly what I would do about it and in what sequence and why. No hedging. No qualifiers. No language designed to protect me from being wrong. Just: this is what I see, this is what I would do, this is how I would do it.

The prospect's body language changed visibly in that moment. They leaned in. They stopped taking notes and started just listening. And at the end of the call they asked what engagement would look like, which is the question that tells you the decision is already made and you are now just discussing logistics.

I have been turning this over all week trying to understand the mechanism. Here is where I have landed. Most consultants and service providers, when they are trying to demonstrate value on a sales call, lean into sophistication. They want to show the depth of their thinking, the nuance of their framework, the range of their expertise. And all of that is real and legitimate and matters in the long run. But in the moment of a sales conversation, what a prospect is actually trying to assess is much simpler: does this person know what they are talking about, and do they have a clear point of view about my situation specifically?

Certainty signals competence more effectively than complexity does. A clear, direct answer to the question the prospect is actually wrestling with, even if that answer is nuanced or involves some version of "it depends", lands harder than an impressive tour of your methodology. Because most prospects have talked to plenty of people who are technically sophisticated but communicatively vague, who know a lot but are unwilling to commit to a point of view without six caveats and a disclaimer.

Someone who walks in and says, without hesitation, here is what I see and here is what I think you should do. That reads as rare. Rare things are valuable. Valuable things get hired.

I am filing this one under things I know but keep needing to relearn. More certainty. Less hedging. Call the problem by its actual name and tell them what you would do about it. The sophistication earns the relationship. The certainty earns the engagement.

What These Three Things Have in Common

Looking back at the week now that Sunday has some distance on it, I can see a thread running through all three of these lessons that I did not notice while I was living them.

All three are about the gap between the version of something that exists in principle versus the version that actually functions in practice. A system that is not documented exists in principle but fails the moment you need to hand it off or rebuild it. A sales approach built on showcasing sophistication rather than speaking with certainty sounds impressive in principle but loses deals in practice. Identity debt is by definition the gap between who you are in principle and who you actually function as when the pressure is on.

What the week kept handing me, from three different directions, was the same underlying observation: what you intend to do and what you actually do are two different things, and the only way to close that gap is through specific, concrete, unsexy actions. Not better intentions. Not better frameworks. Not better thinking about the problem. Just the next actual step, taken without waiting until the conditions are ideal.

That is probably the only lesson any of us actually need. Everything else is elaboration on a theme.

Good week. Rough edges and all. See you next Sunday.

One step, one day. Grace over guilt.

— Dan Kaufman