Schedules: Too little or too much

This is an examination of conscience (of sorts). I have rejected the idea that people can be busy (much as it is a badge of honor to claim as much), but more of stressed/surprised/over-scheduled/etc. I question if there is a linear limit to an individual’s output and if there are ways that this can be increased. I touch on strategies that can virtually make this limitless and even reduce the human toll.

Revisiting my website hosting architecture

In this recording is a review of my current web hosting architecture as I see it after several months of active use. Specifically, I cover the shortcomings of the current setup, ways around each one and advantages of each alternative. This post mainly sets the stage for future updates or posts…

  • What are the core needs?
  • Review of my current setup and available alternatives
  • Discussion of the advantages and disadvantages of each option
  • Next steps

Workflow: Audio & location [bonus]

This is a followup review of process improvements. In a quest to break away from my desk as the sole recording location, I am testing the audio quality when recording from a phone, tablet, in comparison with the MacBook (keeping the application standard). I initially thought that the output was of comparable quality, but I am realizing that the tone variation (especially for tablets) is too great. I also notice that the audio levels are inconsistent as the iPhone version of ‘memos’ does not provide a way to adjust them.

I will do additional testing using Garage Bank on the phone; to determine of that provides better control of the levels and tone.

Dependable dishwashing

I like having machines (and any system) that has a predictable input and output. Dishwashers are the machines that have thus far not given me dependable results. I know that a laundry machine will not scrub collars; and it lives to that performance standard every time. I am working researching how to get consistent value from my dishwasher – this is a review of the process.

Please note that the audio level is lower – I am working on a way to standardize it going forward.

  1. Effectiveness as defined by the ISO-9000 (extent to which planed activities/results are achieved to the planned level)
  2. Baseline of a dishwasher as an energy inefficient rinsing machine
  3. Inconsistent washing of dishes based on positioning and level of soaking
  4. Inability to keep dishes stacked for the whole day

– Consistent quality and results that presents MVP value to justify the wait and cost
– Disruption caused by fluctuations and unplanned cost of corrections to meet minimum expectations
– Establishment/standardization of pre-work that can get the inputs to a level that can assure the desired outputs and justify the costs (delay, value-add, time savings)

Mind like water – Stress-free productivity

This topic is way bigger than any few-minutes could cover – in fact, human beings have spent a good part of the known past trying to do more and better.
My focus here is about the appearance of productivity, really getting important things done, and doing so with minimal mental weight (stress).

Tasty! Recipe for low cognitive-load productivity

Beginning with a pedestrian item (a loaf of bread), I examine the process that is necessary to produce consistent results and eliminate variability by understanding the inputs for predictable output. I then touch on how this is echoed in GTD, iProcrastinate (Tim Pychyl), and Agile project management. The common theme across all the above is the definition of the desired result, and the break-down of the seemingly complex result into constituent steps that in themselves have little variability. It is a combination of a production-line and a chemistry experiment to produce tasty stuff.
Being that it is repeatable and can be progressively improved upon, it allows for limited experimentation by tweaking selective variables and measuring the output.

Improving my audio [bonus]

Quickly dropping-in to talk about my assessment of the current recording setup, and steps that I am taking to improve it as we go forward.
I will periodically do a pit-stop review (such as this) as I learn and seek to improve the quality and efficiency of my output.

How I do this: Simple process

This is a description of my no-frills and MVP technology setup. I walk through the workflow and technology stack that I use to produce the audio posts that show up on my podcast. I am keeping this as simple as possible to reduce/eliminate the friction/inertia of getting this done and hosted.

I could do more, I could make it fancier, I could produce audio with perfectly tweaked levels as Charlie Roberts and Jeff Warmouth trained me to do some 20 years ago at Fitchburg State College. But I choose to make this workflow simple, MVP, and free of the possibility to start geeking on perfect tech at the expense of the bigger goal.