ReRouted has taken a well deserved reading break. However, reading break for myself is a more study intensive time than a normal given week. After weeks of delivering content and hosting interviews, this week will be slightly slower in terms of processing. ReRouted has paused to regroup and plan our next steps in terms of guests and business processes. As mentioned previously, ReRouted needs to design a logo that users can identify our brand with, and although reading break is generally a good time to partake on projects, I have two midterms approaching immediately following the break in Managerial Economics and Managerial Accounting. I’m putting my priorities first, and for now, it happens to be a few other commitments before an interview, which as you may assume, takes some time to plan, complete and post. Balance is fundamental to success, and in trying to maintain this, my focus is elsewhere. Check Forbes Magazine’s piece on the importance balance here. Moreover, take a look at this for an engaging piece on the influential power of building anticipation in consumers through encouraging waiting. 

On Friday, we will resume class and of course, ensure adequate time and effort is invested into ReRouted’s weekly content and Pub 201’s content. This return from break will be introduced with an opportunity to engage in another interesting Peer Review, which will be followed by a discussion post due this week. 

Without having a lecture, guest speaker, or readings to talk about as a Process Post, I surmise this would be a good time to explain what goes on from the other side of ReRouted! 

At the start of the semester, I reached out to many of my friends and classmates to bring them onto the podcast. I used this process to implement a schedule and develop a plan for weeks that I believed were going to be busier. For example, this week being before midterms is extremely time-crunched and therefore had a podcast previously recorded to be able to give viewers consistent content. In the early stages of the podcast, after a guest would agree to an interview, I would drive to connect with them and record ourselves in a quiet room or area that was relatively free of distractions or sound. Upon reflection, this system was logistically easier and seemingly more intimate than what I am utilizing now, and despite being recorded, I believe guests felt more comfortable and willing to be open about their personal story in locations they had greater influence in selecting. As I tell everyone before we begin the interview, the route of their podcast can take whatever form they’re comfortable with. Whether it be positive and happy, or deep and motivating, it is their story to share and I do not want to influence this, making them feel less comfortable which ultimately jeopardizes the authenticity of the interviews. More recently, we have been afforded the opportunity to interview people in the SFU maker commons. This development has allowed for better audio quality and professional editing, as well as a feel of professionalism to the podcast and for guests – if they prefer this experience. However, this adds an additional challenge to the process; guests having to travel to Burnaby Mountain. This can be particularly difficult and frustrating if they do not attend SFU, do not reside nearby or have limited access to transportation. 

After recording the actual interview, it is processed and edited to ensure that quality is great and the volume won’t hurt your eardrums if you listen to these podcasts with headphones. Using WAV files and the Tuxedo Big Files Uploader plugin on WordPress, the audio is embedded onto a post. The idea for having a post for each podcast is because ReRouted wants to make sure every guest is acknowledged for a week and not passed by as just another upload. I’ve linked several other podcast website formats and do believe that this method of post is the most efficient at our level of output. Finally, the posts are written up and approved by guests for you as a viewer, to listen at your convenience.

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php