Okay, so let me tell you about this whole Brian Schell thing I went through. It wasn’t exactly smooth sailing, let me tell ya.
I remember bumping into his name, I think it was tied to some game design ideas or maybe workflow stuff? Can’t quite recall where I first saw it, probably scrolling online late one night. Anyway, the stuff attributed to him sounded pretty smart, you know? Like a clear way to get things done, especially on tricky projects.
My Big Idea
So, I thought, “Alright, I’ll give this Brian Schell approach a shot.” I had this little side project, kind of a hobby thing, that was stuck. Felt like I was just spinning my wheels. I figured maybe his method, whatever it was specifically – the details are fuzzy now – could give me that structure I needed. Seemed logical on paper.
Getting Started (or Trying To)
First thing, I tried to really break down my project the way I thought his method suggested. Spent a good weekend just planning, drawing diagrams, the whole nine yards. Felt productive, you know? Like I was finally getting organized.
- Mapped out the steps.
- Tried to define clear inputs and outputs for each stage.
- Set up some basic tracking to see if it was working.
Where It Got Messy
Then came the actual doing part. And man, that’s where it started to fall apart. The real world, my actual messy project, just didn’t want to fit into those neat little boxes I’d drawn. Every time I tried to follow the ‘Schell way’ strictly, something else would pop up that didn’t fit. It felt super rigid.
I pushed on for a couple of weeks. Kept telling myself, “Stick to the plan, trust the process.” But honestly? It was slowing me down. I spent more time trying to force my work into this structure than actually doing the work. Got pretty frustrating. Felt like I was wrestling with the system instead of building my thing.
The Result? Meh.
In the end, I kinda just… stopped. Not consciously at first, but I found myself drifting back to my old, chaotic ways of doing things. Bits and pieces of the planning stuck, which was maybe useful, but the grand ‘Brian Schell method’ I tried to implement? Nah, didn’t work for me. Not for that project, anyway.
Maybe I misunderstood it. Maybe his ideas are better for different kinds of work, or bigger teams, I don’t know. What I do know is I spent a chunk of time trying to follow something that just added friction for me. Live and learn, right? Sometimes the fancy-sounding methods aren’t the ones that actually get your job done.
