Reclaimed Rails Brewing Company: A Startup with WorkFlowy in the Mix

blog-book-button

I had a chat with Chandler Parsons about the backstory of how Reclaimed Rails Brewing Company grew from “Thirsty Thursday” banter to become a truly unique destination brewery in the State of Iowa, showcasing their passion for hand crafted beer. Chandler is one of RRBC’s 4 co-owners who officially opened their doors to business this last December 20th.

FRANK: Are the 4 co-owners related or just good friends? How is it that you ended up throwing your lot in with the team?

CHANDLER: Two guys walk into a bar…..no seriously, this is literally how things started! Jeremy, JC and I all worked at the same company last fall and started doing “Thirsty Thursdays”. This consisted of a bunch of us guys going to a local bar after work. Well… Jeremy found out I had a homebrewing background and asked if I made it, would it cost less per beer for all the guys. This led to him saying, “Ya know, I’ve always wanted to open a brewery, do you want to be the brewer?”. I said that it was a great idea… but brewing on a commercial scale was much different than homebrewing and I probably wouldn’t be able to fulfill the head brewer role. But I still entertained the idea. Many days and beers later, we actually had a business plan written and were moving forward with this crazy idea!

Co-owners: JC Obrecht, Jeremy Boka, Dave Coy and Chandler Parsons

FRANK: What is it that you focus on and bring to the table?

CHANDLER: My focus, being the geeky type, is all the backend tech. I set up the website and our point of sale, do all of our bookkeeping and help manage the facebook and twitter accounts!

FRANK: Was this a business opportunity for you or has opening a brewery always been on your bucket list?

CHANDLER: Opening a brewery was never on a bucket list but once the opportunity presented itself I decided to run with it. I have a tattoo on the back of my arm which says “One Life”. This is a daily reminder to me to do everything possible today because you only get one chance. I knew this would be a major undertaking but decided I would kick myself in a nursing home 50 years from now if I didn’t at least try the brewery thing!

FRANK: Besides being housed in a former two-story legion hall built in 1948, what makes the RRBC such a unique destination brewery and taproom? Is it a one-of-a-kind setup in Des Moines or even Iowa?

CHANDLER: Besides the building our name represents a number of things:

(1) Iowa is becoming one of the biggest states for supporting its local bicycling community. With that, bicyclists like to frequent bars and breweries during their rides. Our taproom sits one block off of a bike trail that will soon be connected into the future 100 mile loop of trails. Most of the bike trails in Iowa are converted railways, which plays on the name Reclaimed Rails. I am an avid bike rider and couldn’t be happier to be able to help support this growing hobby.

(2)  Our head brewer, Dave Coy, used to brew at a longstanding brewery downtown Des Moines that closed its doors early last year. He was planning on heading out of the state to find work but we were able to help secure his brewing heritage here in Iowa by bringing him AND his equipment to RRBC.

(3) We’ve tried to use as much reclaimed materials as possible when constructing the taproom. For example, the bar is made from four different reclaimed pieces. The front of the bar is made from 116-year-old train depot wood, the top of the bar is made from old semi-trailer flooring, the bar footrest is made of old train railing and the bar is nailed together and features nail hooks for purses and coats, made from old date nails — or railroad nails. And that’s just the bar! The brewery also features a deck made completely from wood, repurposed from the infamous Log Ride that was torn down this past year at Adventureland, the local Amusement Park.

FRANK: Could you run us through the anatomy of your brewery and taproom?

CHANDLER: Our brewery is split into three rooms for production in the lower level of the 5,000 sq foot building.

The first room consists of the mash tun and brew kettle. The mash tun is used to “steep” the grains at a certain temperature to convert the grain’s starches in to fermentable sugars for the little yeasties to eat. The grain is then rinsed with water to remove the sugar and transferred into the brew kettle. We heat up this “wort” to boiling. The boil time is all dependent on the specific gravity being desired and based on bitterness. Bitterness refers to how much and for how long hops are added to the boil. The longer the hops are in the boil, the more bitter the beer will be. From there, the “wort” is pumped into the fermentation tank(s). Yeast is introduced to consume the sugar in turn producing ethanol and carbon dioxide as a byproduct! After the yeast have finished doing their job, the beer is then pumped into the walk-in cooler, which houses bright tanks (AKA serving tanks). Once inside the serving tank, CO2 is applied to carbonate the beer to the correct levels based on the style of beer. The beer is then served directly out of these tanks by hoses which run thru the floor to the bar directly above it!

FRANK:You have 16 tap handles in your Taproom. That means at least 16 different flavored/ crafted beers (Everything from a “crisp pilsner to an imperial stout”). Where along the line from your fermenters to the taps does the beer get its flavor?

CHANDLER: Good question. The beer gets most of its flavor from the type of grain/malt used as well as the hops and yeast. All three of these contribute to the final flavor. Other ingredients can be added as well (Coriander, etc.) to impart a distinct flavor profile.

FRANK: What were some of your biggest challenges in giving this project legs and making it a reality? Were there any “make-it-or-break-it” obstacles along the road?

CHANDLER: Getting financing proved to be an initial challenge. We ran into a few that didn’t want to take the risk simply because they didn’t know enough about the industry. Luckily we found one that had already funded two other breweries within the last two years and they made things happen for us. The other challenge was finding the right building in the right location. We wanted to make it a unique experience and like no other in the metro or in Iowa for that matter. After a few months of searching we found an amazing two story brick building built in 1948. We fell in love with the character it possessed and put in a ton of (sweat) equity to make it one of the neatest taprooms I have ever been in. To answer your second part of the question, there was a period of about 2 weeks were we weren’t 100% sure if we were still moving forward or not. This was after we had raised money thru crowdfunding but before we had received a loan to start construction. Money was tight and we weren’t sure we were going to receive funding!

FRANK: We’ve had a couple of chats via email about task management in general. I know that you were splitting your tasks between WorkFlowy and OmniFocus… and just recently decided to go all in with WorkFlowy. Could you give us a couple of snapshots of your WorkFlowy setup thus far?

CHANDLER: I only switched over completely to WorkFlowy about 2 months ago so its not very robust and may be kind of boring for the WorkFlowy community to view. This first snapshot is a basic overview of my tasks:

Here is the calendar I use for all payments or due dates. I have filtered for just brewery items since I also use this for my personal due dates:

From early days to open doors:


Get EXCLUSIVE bite-sized  WorkFlowy  updates: tips, tricks & news about FREE online workshops with Frank Degenaar. Sign up here.

 

 

Author: frank.dg

Author of the book, "Do Way, Way More in WorkFlowy", I blog on ProductivityMashup.com and for the WorkFlowy blog.

11 thoughts on “Reclaimed Rails Brewing Company: A Startup with WorkFlowy in the Mix”

  1. Same here: I have ditched Todoist a while ago when your Kanban Calendar ( KC ) “clicked” with me. I can’t and don’t want to go back.

    The most exciting aspect of WorkFlowy is, apart from its simplicity, the fact that I can “enhance” it however and whenever I like.

    1. Interesting thing is that my “Kanban Calendar” has its incarnation in Todoist, OmniFocus and all the rest – but it requires that you forgo the bells and whistles that make these apps so attractive. Only when it comes to WorkFlowy, you get to do Kanban within Kanban as deep as you want to go. Not so with other apps.

      You’re right that you can “enhance” WorkFlowy however you want. You’re one of those who is able to take WorkFlowy and reinvent workflows in a way that is tailor-made to what you need.

  2. “its not very robust and may be kind of boring for the WorkFlowy community to view”

    The beauty of WorkFlowy compared to other apps is that it can be as simple or complicated as a user needs. I appreciate seeing how others are using WorkFlowy. Thanks Chandler and Frank.

    1. Every day I am constantly reminded how agile workflowy is not only for storing information but for getting things done. Yea it took me awhile to forgoe the bells and whistles and jump out of my comfort zone losing all the reminders, but it has been well worth it every time I go to search for things and the live results come back instantaneously. Or I add a new task and simply type #avail or #computer without having to hit another 3 buttons just to add a context!

      1. I see the “one life” tattoo you were talking about on your right arm 🙂 Yep, with one life you don’t want to be hitting more buttons than you need, ha!

  3. I am reminded more and more every day just how agile workflowy is not only for storing information but for project management as well. It took me quite awhile to get away from all the bells and whistles of the big project managers, particularly Omnifocus. I can live search and edit a project lightyears faster than in Omnifocus. Do i miss the rigid structure it provided, a little, but that is no longer outweighing the agile*ness of workflowy!!! I think I need to send these two workflowy founders a free crowler full of beer!!! Frank I would send you one but the shipping my put us out of business where you’re at!!!

    1. Yes, WF is much faster than OF, which is one of its strengths. But I still think that OF is a better integrated platform for personal GTD if you don’t need to work cross-platform. The mobile app is much better. Applescript add-ons, like the templates package make it really fast to set up new projects consistently if you have certain workflows that happen all the time, as I do.

      This kind of stuff really increases the odds that you’ll put more stuff into the program and use it. If capture is too time consuming, you’re not going to use it.

      Of course, I prefer a more structured environment, and since I view GTD as a relatively structured approach, OF does a better job of making that structure explicit (as you say). Indeed, after doing GTD for 8-9 years now, I think it’s best to see it as a discipline. You accept a structure and learn how it works in the interests of not having to think a lot of about it after a while. It’s kind of like practicing your scales everyday on the guitar, so that you can improvise based off those scales when it’s time to perform.

      OF was a big part of my being able to do that with GTD. I’ve managed to make WF work for GTD and it’s one of the better options for non-mac users, but I have to use other applications to to make it work (e.g., create my templates in Word with an add-on called simpleprompter and then paste them into WF).

      If I hadn’t already spent a lot of time in OF doing GTD, I think it would have been hard to make it work well in WF. The lack of notifications/reminders is also an annoyance. I have to put those kinds of line items in Wunderlist or Google Calendar.

      I know the Unix approach is one small tool for each job. But to the extent that the GTD idea is to have one trusted system where you dump stuff until you need it, a distributed network of little tools increases the odds that information will fall through the cracks (e.g., I enter a line item WF that needs a reminder, but I forget to enter it into into WL and therefore don’t get the reminder that I need).

      Anyway, I love a lot of stuff about WF, and it’s very good at the things that it’s very good at (i.e., the outline part). Just wish it was better at a couple of things that it’s not good at (some of the stuff that would really elevate it as a productivity app).

      1. You make some great and valid points here that I can’t help but agree with in regards to bot OF and WF. When I first tried switching to WF a year or so ago, I realized I really needed the structure and couldn’t trust myself enough to not have it. Now, I feel the lack of “structure” has actually helped me focus more intently on what I am putting into the system and not just throwing random crap in there, because I know OF would have sorted it out and reminded when needed. I really hope WF can offer a few more features (reminders, recurring tasks) that I feel wouldn’t bloat the system enough to make it less agile. For a dead nuts due date, I have to use Due on iOS for that. I also just went to Pro with WF so that basically solidified my decision for atleast the next year until my subscription renews! Ha.

      2. Yup. That all makes sense. The agility of WF is a really huge bonus and not to be taken lightly. But I’d love to see a couple of those features you reference. The bookmark feature in WF already gives you something similar to OF’s perspectives feature (although I think you can do more complex searches in OF).

        I’d love to see find and replace also. the import and export in WF works surprisingly well, though.

        And WF is probably a better platform for shared task lists. So it’s a bit of a wash. I miss OF sometimes. If it was cross-platform, I’d probably consider going back. But it’s not, and Omni seems very hardcore about staying Mac only, so I can’t see that it ever will be cross-platform.

        Therefore, unless something way better comes along, it’ WF for me.

        I’ve looked at Moo.Do and Dynalist. Each has some of the stuff that WF lacks, and on the surface, they seem similar in look and feel. But at least so far, neither one is nearly as elegant in actual practice.

        With luck WF devs will be able to add a few of those missing things without sacrificing that grace.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s