Who You Calling A Jesse?

This past week I have had my calendar and task list hijacked by a cold virus that hasn’t even found its way to make me ill but it has decided to drive up the internal temperatures of the two little things in the house. The upside to this is that I have an excuse to hang out with them during the week, the downside is that this unplanned vacation is anything but and I am sinking into declaring inbox and task list bankruptcy.

How do you balance kids with work?

Honestly, how do you? You don’t, kids win every time. However, how do you deal with coworkers that find your unplanned absence annoying? The situation for my wife and I is extra fun as she just recently returned to work from maternity leave and they are already down one staff member in their group, I am working on a startup when I am not working my more than full time job at VeloCity, and I still have responsibilities as Past President of the UW Staff Association. Thankfully we both have understanding coworkers but not everyone does.

• Work with your partner—even though you both won’t be sleeping and probably have short fuses
• Prioritize the big things and find an hour in the day to triage (see it as being forced to focus on value, not volume – that might help)

Then repeat the following every time you think you are about to drive yourself crazy with thinking about the things you should be doing:

Nobody on his deathbed ever said, “I wish I had spent more time at the office.” – Paul Tsongas

When you are busy second guessing your decisions about going to the doctor or not going given temperature, time, colour of the boogers/poo, should they go to daycare, or damn daycare for the bug sharing, etc you find work is a pleasant distraction but don’t let it guide your decisions. Once in a while I find myself heading that way and I have to keep coming back to what is most important and it isn’t work.

When TEDxWaterloo was first mentioned I was beyond excited (it was around the same time IgniteWaterloo was being planned which is also awesome). The focus and quality of the independently organized TED event is something I think the local community could really benefit from. As much as I love the whole unconference thing I know it doesn’t work for everyone and it can be really strange to people that haven’t attended. However, I am disappointed in the rationale behind applying to attend that TED itself promotes. I do appreciate the views on it by organizing folks but…

I am concerned about it being exclusive

I had a big long rant written about this but instead I will keep it simple: applying to attend something in a community this small that is dominated by Higher Education, think tanks, and RIM-jobs driving BMW’s implies exclusivity. Maybe being exclusive to a certain type of person is exactly what TED is trying to do to ensure there is quality conversation. However, the community is full of interesting and colourful personalities… you can’t just exclude them because, well because is hard to say as they haven’t really listed any measurable criteria.

As one of the commenters on Renjie’s blog post there is a fine line between elitist and open that TEDx seems to just barely stay on the positive side of but I think the problem the registration is intended to fix doesn’t actually exist. Not in Waterloo anyway.

What am I going to do about it? Nothing. I am not going to apply to attend, not going to talk about it anymore (I will try), and look forward to the next Ignite Waterloo or BarCampWaterloo or StartupCampWaterloo or Web Design meetup or startup drinks or any other event that is open to everyone.

Over the past week we tried something different at VeloCity – we opened up the term not with speakers but instead engaged the students in a serious of brainstorming evenings followed by a weekend focused on starting their startup. Amongst the group discussions, team formation, development, and business planning have been a number of local entrepreneurs that have wandered around the residence talking to students and offering some insights—at least one mentor really enjoyed the experience.

The goal for the week evolved a bit but what I wanted to do is give all 65 students at the residence an opportunity to participate early on by challenging them to have a pitch and a demo by Sunday night. Keeping in mind that most (if not all) of the students here have never had an opportunity to work towards building a business with their peers.

The result? About 50 of the 65 students at VeloCity participated this weekend in fleshing out some ideas and most of the teams actually built a usable application. One of them, the room booking application, will be used at VeloCity starting this week!

At the moment I am a bit tired from the 80+ hour work week to write a big post but I can confidently say that we have exceeded out goals for this week and moved VeloCity clearly away from simply a space for innovation to a community that is actually doing something.

Ignite Waterloo was a couple weeks ago and by all accounts it was a huge success. The eclectic mix of brilliant presentations and a great crowd made for a very fun evening. I had the opportunity to present as a fill in for Mark Kuznicki who was going to talk about Changecamp and the power of community. It was fun trying to pull together my thoughts into a 5 min presentation. Have a look!

Jesse Rogers: The unconference for fun and the goodness of community from Ignite Waterloo on Vimeo.

I find it very strange to watch myself present—makes me cringe at times. Who likes the sound of their own voice? Honestly ;)

Have a look at the other presenters in the Ignite Vimeo channel and you get an idea of how great the event was. My favorite is probably Dave Estill on Solar Energy followed a close second with Simon Clark talking about Hacking the hood.

As December sets in on campus the IT staff get a chance to huddle around Ron Coutts Hall (RCH) and get together to swap some stories along with learn new things at the WatITis conference. I have blogged loads about this in the past as I have enjoyed every single one since they started. It is a great way to find out what the heck is going on this large campus and put some faces to email addresses (not many on twitter, yet).

This year I am presenting on baby steps in an agile world (slides below). It is a slimmed down, more focused version of a presentation I did at Higher Education Web Conference in Milwaukee this past October. I took the feedback (thanks for the feedback folks) and slimed it down, focused on real practical tips for agile techniques, and I think I have a good 30 min presentation. Which leaves 15 minutes for discussion—something requested by the organizing committee.

Since no one will probably do it at the keynote I will set the hashtag now as the obvious #watitis09 (watitis without the 09 is a pretty funny hashtag to follow) and keep the realistic expectation that there will be a hand full of people tweeting ;) Looking forward to the day.

Over on the VeloCity blog is a request for support from students at U of Waterloo for what we are calling a Centre for Student Innovation. The idea is to provide an office somewhere on campus that is more accessible to students that we could offer things like co-working, office hours for off campus entrepreneur resource/mentors, and find out more about the amazing entrepreneurial community here in Waterloo. Sorta like a VeloCity club office of sorts.

What we need are email from U of Waterloo students(to velocity at uwaterloo.ca) in support of this idea. It seems a bit crazy to think we need that but we really do as there are a lot of good groups on campus competing for very limited office space. I think VeloCity has the best idea but I am biased. It would be great (and easier) if a few really successful entrepreneurial UW Alumni wanted to maybe donate some resources to expand or build something for VeloCity, any out there reading my blog?? ;)

Until those investors arrive, we do need those emails to make that happen. Please spread the word, retweet, make a facebook group in support!

They did it again, Communitech pulled off an amazing week in Waterloo focused on entrepreneurship. With some great speakers (Ali Asaria, Jim Estill, Tim Bray, etc) and a great events (Gala, StartupCampWaterloo, Founders and Funders, etc) the week was a rather intense week of networking, learning, and having fun. I had the opportunity to attend most of it and there were a couple themes coming up in conversations…

Talent, money, opportunity

The number one discussion item is where are the people to lead local startups, develop them or develop for them, and ensure they succeed. The stories range from not being able to pull senior developers from their high paying jobs at RIM to statements like “all Canada’s top talent leaves.” It flows directly into money.

If a startup is trying to bootstrap or has just enough revenue to grow but grow slowly it can’t offer the 100K+ salaries that some local companies offer for the most talented and experienced folks in town or those willing to come to this town. That is probably the big advantage startups in the US have over their Canadian counter-parts in that they are normally better funded earlier on and offer a more interesting life style that makes up for less pay.

However, I don’t believe that. Canada’s top talent is here in Waterloo. They are going to school here and making decisions on their future. The opportunity is here to sign them up to entrepreneurship young and develop that talent locally and I think a big piece of doing that is connecting them to their peers on a different level than simply academic.

The missing component: a belief that you can do it yourself

I have a nearly three year old son, I am his parent and his mentor (along with my wife). How do I guide him? Am I required to? He is fiercely independent and at the moment needs me to stay out of the way and simply (or not so much) keep him from hurting himself too badly. That is an entrepreneur to me. Someone who is constantly pushing the rules, the boundaries, and not taking direction literally. They don’t read instructions, they don’t follow the rules, they see all that stuff as guidelines and principles. Every minute of every day they are learning, adapting, and trying a new way to do something.

That all has to be tempered with the ability to know when to turn off that behavior/instinct and simply play the game to achieve their goal. That goal could be their undergraduate degree or that goal could be to ship a product and start generating revenue even though they themselves might not think it is awesome enough.

Mentors as (and) peers are essential to help entrepreneurs learn to harness their curiosity and drive.

It is about community

You can not underestimate the value of community. I absolutely loved the Founders and Funders event but at the same time it was intense speed dating compared to the open and fun atmosphere at StartupCampWaterloo. I found Founders and Funders a much better event because of the other community events where I have had the opportunity to interact with a lot of the same people in a less formal atmosphere—many I consider my peers or mentors.

Locally we now have community events like: StartupDrinks, DevHouseWaterloo, Web Design Meetup, Social Media Meetup, BarCampWaterloo, StartupCampWaterloo, DemoCampGuelph, MoTH (I think), Ignite, and likely others. These events level the playing field and support the idea that there is not a hierarchy with experts or gurus but a peer driven community.

I will say it a thousand times; money, speeches, and mentors do not create a thriving entrepreneurial community. It can compliment a community or they can hinder community growth or worse perpetuate a class system that might be applied to entrepreneurs (classes defined by age, experience, education, background, etc).

Waterloo is lucky. Communitech, the Accelerator Centre, VeloCity, CBET, TechCapital, and many other organizations are here contributing to the growth of the community at a number of different levels for a number of different big players. Momentum is growing… the best is yet to come.

Over the last couple of months Joseph Fung and I have been working on a little project in a localized community site that assist the local tech community find out what the heck is going on around here and who is doing stuff. In the process we developed a site that could do it for a lot of other communities—we think. At the moment we are calling it Agnostic Platform and you find the Waterloo version at waterloo.techstartup.ca where we have a roughed in application and some warts showing.

The idea is to provide an open place that is semi-moderated by community connectors (a the moment Joseph and I are self-declared connectors) that can maintain the garden of awesome local information. Our experience/assumption is that automated attempts at local news, blogs, twitter, calendar, etc information is prone to both spamming and error. You need people in the community to ensure the quality but you also need to be open about who is included and why.

We hope that a site like this will help people (both new and longer term residents) make better connections with some of the amazing folks locally and find out what is of interest, what is going on, and who to contact. To do that it will need more community connectors involved, people contributing links, feeds, events, blogs, etc. The only rule for content streams is that the content creators are local. They live locally, they contribute locally, and it is even better if they participate locally.

It is a bit of a work in progress so please give us feedback and use the site. I am really excited to what we can do with this.

Communitech’s blog posted something about it as well.

On the way home yesterday I wrote this post in my head about dozen times. Lots buzzing around after some great discussions and some late nights in Milwaukee. HighEdWeb is by far the best conference focused on web technology, strategy, and networking in higher education. It isn’t because of the speakers (although some were simply amazing), it is because it brings together people from the most diverse collection of schools from across North America all with similar problems but different solutions.

Messages I kept hearing:

• Web teams in some schools are already starting to evolve as they grow while other schools still have layers of committees (Web Task Force – WTF – is my favorite) duplicating work and removing accountability. Not many teams of one left out there.
• Usability testing is required, it is not an option. I would slide towards more of ‘usability monitoring’ along with iterative improvements is the way to go. Not many schools are there yet but enough are going there to see a trend starting.
• Engaging your audience using Web 2.0 tools with Web 1.0 thinking doesn’t work. You probably don’t know you are doing it.
• CMS deployments solve one problem, create many others that aren’t as bad as the original problem. No surprise here.
• Problems or challenges: budgets are being slashed, recruitment is getting scary, web initiatives are underfunded even though they could have a big ROI.

There were some extremely entertaining moments around the keynote from the second day. The presenter was well out of touch with the audience, slides were poorly designed and outdated, and his content was poorly delivered. He got mobbed on twitter (and isn’t on twitter himself even though his topic was on using the web to engage your audience) with the outside audience reacting in a funny way. The backchannel was rough on him but honestly if I did that I would expect the same reaction.

As for my presentation, I think it went ok, people seemed to appreciate it. I got totally nervous given how packed the room was though. I am sure they noticed but nothing nasty on twitter ;) In retrospect, I tried to cover too much in a 45 min slot. I could have easily broken it in half and I think people would have got just as much out of it. Project Management is a workshop, a lighter overview is a presentation. Maybe they will let me do that next time. Really looking forward to HighEdWeb2010 or 101010. My slides are here:

Last night at DemoCampGuelph Joseph, Stephen, and I demo’d our little side project… an app for taking the simple HR functions out of a spreadsheet and dropping them into a web app. Our big goal is to change the way people think about HR, for now we just want to make it easy for people to give feedback to each other, state their goals, and manage a few simple things like vacation. We call it TribeHR and at the moment we are really close to opening up a beta for a few folks.

Our site is missing some details but those will be filled in over the coming weeks. I am really excited about this little project as it seems to resonate with a lot of small businesses and startups that want to do something but they just don’t have an affordable tool.

Over the next few weeks I will probably talk lots about it. Hard to get feedback until people can try it out I know ;)

The new UW logo continues to create a stir with the request for feedback on the new logo and a couple alternatives. Pretty much immediately after the request went out UW Opinion was lit up with a range of colourful commentary, some useful suggestions, and some posts that are way out to lunch.

With regards to the new logos I don’t have much to offer about any specific design but I still think the staff at UW could do way better. I don’t think they will though as the process is broken (something I mentioned in my post back in July). A post by Sanjay on UW Opinion touches on it as well.

I think a big part of the problem with the logo boils down to an organizational cultural one that speaks to how people value art, communications, and design in this community. Over the years working at UW I have had a chance to work with many talented designers that have been treated as contract staff that are to simply create exactly what they are told. They aren’t seen as authoritative talent that was hired to handle ‘how things look.’

Usually what happens to the designer is they are forced to use bad photos, odd fonts, colours, and layouts as dictated by the client when they know they don’t work together. What it comes down to in design consultant terms, staff groups at UW are the nightmare client that you can’t get away from because it is your full-time job. They aren’t allowed to do what they are hired to do…. and yes, I said staff groups at UW are nightmare clients. I have been on both sides of it and I don’t think people do it intentionally but I do think people in general do not value the skills and expertise of others—particularly design talent.

It is likely that a lot of other higher ed institutions suffer from this organizational culture issue.

What I would ask from the leadership in higher ed in general is to let professionals do their jobs, don’t let them step outside their roles and step on the jobs of others, and understand good design can not be done on the cheap. Otherwise you will have burned out staff that feel overworked and under appreciated—the type of people that shut off and loose the passion for their work.

I should add… a lot innovation, personal growth, and good experience comes when people step outside their defined roles. My point is that people should be challenged to step outside their roles in a more strategic way. It should not just be normal that an admin assistant takes on a co-ordinator role for the admin assistant pay or worse take on the role of a co-ordinator that is already trying to fulfill that role.

The fall term at VeloCity kicks off with a one day conference that aims to set the tone for the term and introduce the students here to some of the community’s greatest assets—the people. Speakers for the day include:

• Ali Asaria, Well.ca
• David Crow, Microsoft BizSpark
• Ilya Grigorik, PostRank.com
• Jacqui Murphy, TechCapital
• Steve Lightstone, Corner Office Leads

Along with some folks from PriceWaterHouseCoopers the day should be filled with some great conversations. We start off at 9:30am with a breakfast and close out the day by 3:30pm and the event is taking place in RCH. We do have tickets available to non-VeloCity residents with different rates for VeloCity Alumni, students, and community folks. The spots are limited so please only register if you are sure you can come.

Since I have something to do with the organization of the one day conference I am trying to make this as unconferencey as possible but we do have an agenda (will post the PDF soon). There is also a new VeloCity site coming next week—which is where stuff like this will be posted as well.

Starting in September is the first full term that Virginia and I will be able to guide how things work at VeloCity. I am really excited to change things up a little and offer some events that I think are more inline with what the outside-the-uni startup community is use to seeing.

Some things we are keeping:

• Startup conference on the first Saturday of the term. We are calling it VeloCity 101.
• Bringing in speakers when they are available to offer some insights on experiences.
• Working with community partners to help enhance the overall experience and resources available to students at VeloCity.

Some things that are sort of new:

• More things that involve whiteboards and building ideas into products.
  
  • A regular schedule: Alternating Monday nights with Tuesday mornings and offering a brainstorming/social/discussion on the Monday night and a breakfast networking/talk event on Tuesday.
  • The first Saturday conference will try and reduce the lectures and engage in conversation.
• Invite the larger community to participate and getting the students in VeloCity to participate in the community events.
  
  • This means demos, talks, etc.

…and so far that is all we have. We will need to react to the needs of the group but my goal this term is to have 100% of the students in the residence actively engaged in the discussion and over 66% building something… even if it is simply a lemonade stand in the SLC.

I had some fun with the Spring term even though we were still trying to find our bearings jumping into a program that is moving so quickly but I am really looking forward to the fall term.

One thing that really been highlighted to me by the University of Waterloo logo fun (#uwlogogate) is that committees are overused in higher education and the quality of the work could be suffering. Even if the quality might not improve I can’t see how committee work isn’t contributing to an increase in work load and stress. This happens because (using this current issue as an example) a committee (or a series of committees) appears to be responsible for:

1. requirements, strategy, and execution of the branding work
2. logo research, design, and approval
3. communications planning

How the day to day works is that you have a number of staff from different departments with different reports and interests doing their normal job and working on the branding stuff essentially on the side. Focus is not 100% on the task, it can’t be. The result, a decent logo but one that meets the needs of very specific, unfocused, and likely insular interests.

A project needs to be a real project

What I think is wrong is that a committee of staff with other jobs should be responsible for:

1. high level requirements, strategy, and oversight of project

Then a project team is to do the work, report back on how what they are doing is inline with the vision/values, and get the job done. A project team that is doing it full time reporting to one Project Manager and sharing a common interest.

The project team will have the added advantage of spending enough time on something to develop expertise that it might be missing. It is really hard to be really good at something that you don’t have the time for. It is likely the quality of the work suffers because the expertise just isn’t allowed to develop with the project.

This actually gets really bizarre when you look at things like hiring committees and search committees. The membership is made up of ‘representation’ but not by people that are qualified (or likely) to understand the requirements of a job for which they are hiring someone. Their positions don’t offer them the context or the expertise yet they are drawn together to represent what are arguably irrelevant interests.

That is why I am not arguing for broader consultation on projects (like logo making). That doesn’t work. I think broader consultation on higher level principles is ideal but when it comes to doing the work let the people you are paying to do the work produce the best work they are capable of. If it is truly sub-par work then something is wrong and something needs to be done.

A committee that is tasked with doing real work removes all responsibility and accountability for the quality and delivery of the work.

You can’t apply good project management to a committee

Can you actually apply project management techniques to committee work? I don’t think so. Sure in MS Project you can claim an asset (person) has 20% of their work week for a project but it doesn’t take into account that with one day a week of time you are probably getting 1/3 productivity on that. The inevitable 1/3 of your day getting your mind focused and working, 1/3 doing work, 1/3 for interruptions.

Too much time is spent on updating progress, lingering issues that aren’t solved, politics in the office back in the home department, etc.

Highered needs to create more temporary project teams and less committees

I believe we need to stop using a faculty influenced process and go to a more business focused way of running projects with a twist. The twist being the project has committee oversight that agrees on the goals and the measure of the project is its adherence to the goals (committees can not say things like “moar lazerz”).

This is a rough thought of course… more discussion is welcome and required but in general we need to change how we do projects in higher ed or continue to put out sub-par work and over stress staff in the process.

A pretty interesting social media incident has occurred here at the University of Waterloo, one that I am sure is causing some people a lot of stress and others entertainment. Short version: UW branding effort had its logo work leaked, students rise up on Facebook!

As someone that started working at UW at the tender age of 25 having my work out in full public view for public stoning I can certainly emphasize with those behind the new UW branding effort. The Facebook group that is acting as the hub of criticism has certainly grown fast and the comments are emotive and colourful (image above left is an example of their ‘protest’ versions and they show UW students are creative!). What has happened thus far? This is my best guess order of events:

• a long time ago the previous VP of External Relations identified problems with U of Waterloo’s brand outside of Ontario. Our Alumni are everywhere in senior positions of very fashionable organizations yet our name isn’t. The school, city, and region all suffer from the “Toronto is the centre of the Canadian Universe” syndrome I think.
• Committees were formed, talented staff were rallied and a very long process began.
• A turnover at the VP level brought some fresh vision and motivation, process moves faster.
• Lots of work, emotion, and discussions later there appears to be some visual identity pieces that started going up on campus this week.
• Students got a hold of some ‘still in progress’ logo work, Facebook group created, the freak out gathers steam.

1. an idea is generated
2. committees are formed
3. they meet
4. and meet
5. they meet with other committees and things are changed to please certain people
6. a careful strategy of ‘getting use to change’ is deployed

Everything went according to the way things do in academia and then a step 5a happened—a digital media problem. Files are leaked and social media rallies the ‘no’ camp before step 6 really gets going. What happens next will be very interesting. Currently the students behind the group have a meeting with the VP of External Relations and I hope from that comes some more factual information to the Facebook group on what is happening and why. A missed opportunity, I think, is having the VP post that information herself to the Facebook group.

In higher education it is about being open to criticism and debate. Social media just compliments what is a long standing tradition. Don’t shy away or worse be dismissal of branding or your position because you will get some lumps from the vocal stake holders… engage them. Although I don’t think a closed door meeting is truly open at least a VP takes the student concerns serious enough to spend time talking to them. It is part of who we are in higher ed.

It isn’t all bad even though I will freely admit I expected more out of a logo for UW. There is more to branding than a jpeg. The banners going up speak of ‘taking risks’ and being ‘courageous.’ Since being an undergrad here I can honestly say I have only seen that in spits or spurts (with VeloCity being an example). However, to me the secondary and maybe more important part of branding is putting out there the values and aspirations of the institution so everyone has a common point of reference. If we say we are risk takers we need to be risk takers. Having it as part of the branding empowers the risk takers vs the risk adverse people. The whole language on the banners thing is a risk… like ‘intelligent community’ the institution will be called out when it does things that seem risk adverse.

As the Facebook group grows it will be interesting to see if #uwlogogate will have legs into the fall. My guess is that this will be a good example of why you need to have a social media strategy as part of your step 6. Assume what you are working on will get leaked and you can’t control the message anymore. It is a real risk and one that needs to be managed.

Note: I have not nor likely will be involved in UW’s branding effort. I left External Relations before it started but I can say that the need to work on UW’s brand has been known for a very long time. Nor am I an expert in marketing.

Today I find myself at a car dealership in town that is willing to sacrifice a long standing relationship for $50. No more $150 oil changes, no more other service, certainly won’t buy new tires from them, etc all because they insist to charge me to figure out what is wrong with my less than three year old Saab. Talk about a short-sited customer service decision.

After leaving my car to sit for a few weeks while I was on vacation I returned to a car that was just a mess. The lights kept going out, there was a violent vibration from the back wheels (feel it in the seat not the steering wheel), and it just ran rough. Given it is generally a sleep in the garage car I assumed it just didn’t like being outside and/or it is showing its 65K of KM. Although for a Saab 9-5 that shouldn’t be a lot.

I finally managed to get into the dealership a month and a half later. The lights have been an ongoing concern (they have been replaced every time I bring it in) so no worries there, they will take care of it. The vibration might be warranty work or it might not. Just to find out I get the privilege of paying for the time to figure it out.

I realize it is common practice for mechanics to do this. After all, it takes them some time to figure it out (or simply plug in the computer and it tells you) and sure mechanics could spend all day diagnosing things and not get paid. But:

• is diagnosis not built into their $80/hr+ billing rate?
• I bought the car from that dealership and I might buy another (not now)
• The mechanic won’t feel the vibration anyway as he isn’t allowed to go fast enough to feel it (yes it is above the speed limit but not by much)

What I don’t understand is why do people accept this? If more people complained then there is no way it would continue. I am certain the irritation on customers over oil changes is why GM now covers that for the first few years… obviously the service cost is worth absorbing to make customers happy. BMW, Mercedes, and others offer free ‘scheduled’ maintenance as does Cadillac. They probably don’t charge to tell you if something is warranty work or not. Why? Over the ownership time they may have to absorb $200 per customer on average which is pretty cheap for happy people that spend 40k+ on a vehicle.

Our lease is up in a year and I am pretty sure I will not be going back to that dealership for much beyond handing them the keys.

The Canada 3.0 conference wrapped up the second day with speeches from the CEO of RIM, the Chair of the CRTC, and others all with a strong patriotic message as well as a surprising amount of useful vision and position stuff specifically from the the Chair of the CRTC. Day 2 did, sadly enough, start off with some rather dry and boring stuff that made for a fun game of buzz word bingo.

Between the speeches I attended the talk that included Waterloo’s own Jacqui Murphy from TechCapital. She took full advantage of having a mic and an audience to make it clear that startups shouldn’t be about seeking funding or exits with big companies buying you. You should dream big and focus on revenue generation. Some great messages to bring back to VeloCity I think.

The round table discussions in the afternoon felt like they lacked energy and urgency. The big rooms and groups just didn’t work well for that but I did meet some really interesting folks around my table. If nothing else, that was a huge bonus.

Overall, the strength of the Canada 3.0 conference was in the diversity of the folks that attended. There were some very obvious complaints about the lack of students attending but we really need to stop idealizing students, if they are interested they will come—if they aren’t there they really don’t care…. yet. There were enough student volunteers to suggest to me that the ones that are interested knew about it and made the effort to attend.

What I think was really missing was the younger entrepreneurs and leaders on the panels. Not the under-25s that the over 50’s marvel at, but the 25-40 yr old professional crowd that have the skills, experience, and know how to really push Canada’s ‘digital economy.’ I would have also liked to see more of an unconference stream. Being a Barcamp/Startup organizer I am already a fan of the format but we needed more conversation over round table sticky notes. I will even volunteer to organize that for next time ;)

I should also point out the technology situation. Stratford doesn’t have 3G, the wireless was overwhelmed by all the mobile devices and laptops begging for data (but we got the tweets out!), innovative things weren’t set up like streaming panels to the media room at the very least. Sure Igloo put together a good site but that was impressive a couple years ago, if this is ‘3.0’ then it should push the boundaries.

Honestly, it was an amazing conference. This should be the start of something… keep the buzz going, follow up with the business cards you collected, and start thinking big!

The Canada 3.0 started today in Stratford Ontario (45km west into farm fields from Waterloo) and surpassed a lot of people’s expectations I think. The morning had the typical political talk you would expect when government folks are given a microphone along with the University of Waterloo making it clear it is committed to the Stratford campus and all the potential developing such a campus may hold. What followed was a day of great conversation about communities, what to do to foster entrepreneurial talent, mobile technology, and more.

It was high level discussion mostly but it was honest discussion focused not on how great Canada is but where Canada needs work. Have a look at the twitter stream under the #can30 hash tag for some great bits of information. Day 2 promises to be more interactive with work groups tackling some of the issues presented today.

I spent a lot of they at the VeloCity booth talking to people that are interested in the idea and colleagues at other schools that are a bit envious that Waterloo has such a residence. I will be around for day 2, stop by the booth and say hi!

Over the past couple of days I have been driving the Chevrolet Traverse as part of a Twitter Test Drive arranged by Waterloo Auto Mall. Overall I think it is a great XUV (SUV is so 1990s) that does pretty much all of what a mini-van offers but with a much more solid vehicle that you can use on light off-road fun and snowy days.

• Back row of seats—although not entirely usable for adults (what back row is?) there are plenty of seat belts for when you need to move kids around town
• Even with the back row up you have space for stuff—something I didn’t expect given it isn’t a Yukon or Tahoe.
• The 3.6L engine can actually move the thing—it has enough acceleration to be fun
• Overall design of the interior—although not up to European quality of materials, it certainly is well designed and comfortable

• The stock GM technical parts that you see in 20-30K vehicles in this one that has a 50K+ price tag—The quality isn’t there in the 20 year old digital displays compared to similarly priced BMW’s and Mercedes.
• The exterior lighting—again, for the price I would expect xenon lights and less ‘cheap’ looking plastic
• Mileage—this vehicle isn’t broken in but but the avg economy on a highway drive between Waterloo and Hamilton was 12L/100km (~20 mpg). Why wouldn’t I just drive the V8 Tahoe?
• The one I had was front wheel drive only—for the price I would expect all wheel drive.

The two top things I don’t like is (I think) because this model has a 50K price tag but there is a 35K version. That is something that I think plagues GM vehicles as a whole. You can’t upgrade bits here and there and add that much to the price because you start getting into BMW and Mercedes land that have all those features and more in a much nicer designed package with quality finish. BMW and Mercedes just don’t have a lower priced option… GM needs to either upgrade more in a vehicle or stop trying to have premium domestic vehicles.

My verdict

If you can get an all wheel drive version at the 40K level you are getting a great vehicle. The quality, the performance, and the utility is certainly there. However, I am not convinced I wouldn’t look seriously at a Jeep Commander instead if I want a 4×4 that can do family stuff for ~35K.

Also: See the Edmunds report on the Traverse

About TwitterTestDrive

As far as I know the Waterloo Auto Mall is the only dealership trying to actually use social media and reach out to its customer base. I think it is a brilliant idea to try out and let the users of social media reach out to their online friends about a real experience that is essentially word of mouth marketing. I expect the #twittertestdrive hashtag will be filled of some honest and interesting experiences over this summer that will influence at least a couple car buying decisions out there.

Almost ready to have the sixth StartupCampWaterloo in just under two years. For this one it was decided to not get an opening speaker and just leave it to the community to drive the event. Our sponsors are still doing the same thing and making sure everyone has snacks and liquids. I am really looking forward to the event and meet some new folks as well as catch up with others. If you haven’t signed up and are coming, please head over to eventbrite!

After number six there will be some changes coming to StartupCampWaterloo. We didn’t get a chance to put them in place this time due to vacations (I didn’t post a thing in May) and overall being busy. If anyone has suggestions please post them here to drop me an email (jrrodgers on gmail).

After a few weeks of going back and forth with all the internal workings it is now official, I am one of two new Associate Directors at U of Waterloo’s incubator 2.0 residence, VeloCity. I join Virginia McLellan (the other Associate Director) and Sean (Director) as the new team to really push things into something really great (and fun).

The residence has come a long way in last 8 months since it started taking on students. With more investment in people to help push the direction we plan on building more of a community around VeloCity, trying out new things, and seeing where we can go. It is very exciting to be involved in such an innovative and fast moving project.

Can’t wait to get started.

Following what was an interesting 2007, 2008 proved to be one of personal and professional growth. Here is my reflection/projection post for the year.

Personally:

Probably the oddest thing about the last year was that it felt like I got very little done. I just didn’t feel productive in my work life nor did I feel like I was using my own time very well. Sure I got to spend a lot of time with my son and accomplished a lot at work but I think a lack of sleep just left me feeling a bit drowned in tasks for 2008. An overall goal for 2009 is manage my time better and enjoy myself more.

I also need to use more time for a hobby or two that isn’t web tech related. It may be time to re-invest into hockey equipment and/or my bike. At the very least I am going to bring my son fishing and try to get up north more often.

That said, things I feel good about personally:

• I finished my Msc (and my wife finished hers)
• Led the UW Staff Association as it doubled its operating budget, hired an Executive Manager, changed some key policies, and after 40 years the organization signed a formal Memorandum of Agreement with the University of Waterloo.
• Drove to Myrtle Beach, South Carolina
• Besides Myrtle Beach I visited Las Vegas, Orlando, Wilmington, Clarksberg, Georgetown. All except Orlando were family trips!
  
• Spent a lot of time with Addison
• Welcomed an amazing baby girl into our family

Professionally

Working at the University of Waterloo has advantages and drawbacks. The drawbacks are largely the politics of the environment – a culture that suppresses creative problem solving has been set in for some time. I can honestly say that in 2008 I finally figured out how to get things done properly in such a place without becoming part of the existing culture. The organizational culture must (and will) change over time. Not sure if I will be around UW long enough to see it but who knows.

The past year was about being front and centre in campus wide politics. This coming year is going to be about building some pretty cool front ends, learning to really love (and hate) AJAX, AIR, MS servers, and design. I will be more behind the scenes on campus politics hopefully and I just focus on some good geekery for 2009.

I would also like to make a few more conferences this year. The creative spark that I get from conferences went missing last year. I need that back.

Community

This past year saw what I think was a huge success in the growth of a local tech/entreprenuer community outside of traditional channels. StartupCampWaterloo and BarCampWaterloo really started to take off. DemoCampGuelph contributed as well to what is a pretty interesting unconference community. It isn’t a huge community by any stretch but it is a very intelligent group of creative entrepreneurs. I am excited to see what 2009 will bring.

There is of course the other groups locally that add depth to the community. DevHouseWaterloo (hosted at AideRSS), local Twitter groups, Flickr groups, etc are all enriching and broadening community.

This year I want to get a local Adobe User Group off the ground. The region has a lot of Adobe users and I think they could all benefit from having a group that shares their experiences using software from Adobe. Being an Adobe Community Expert I should really get on that ;)

Bring on 2009!

Seems RIM’s new Blackberry Storm has a raised a few eyebrows over web related things. In the first review I read there is a mention on the browser:

…had zero issues with the Storm’s browser. Zooming in and out is simple and it seems to load most pages fine, except the NYTs as it reverts to the mobile edition and doesn’t want to load the regular site. Anything with a lot of Javascript chorks, though. Everywhere else on the device there are scroll up/scroll down keys but they’re missing on the browser. Seems like an odd move, but the navigation bar would be a bit crowded. – CrunchGear

As a person that believes the browser is the platform I think the browser is where the mobile device will be won (or lost). As much as I love the app store I hate having all those silly icons scattered on my device just to access web based content. Let me use my browser (like google does). Likely a balance needs to be found but at the moment I have app icon overload…

Living in the town of RIM (Waterloo, Ontario) I often hear things at pubs, at events, or through some second hand gossip. What I hear is usually some pretty positive stuff but at the risk of calling out a specific person, when I hear something along the lines of “webkit doesn’t support Acid2 but the Storm browser does” as a point of discussion I get a little concerned.

First, the Acid tests for web browsers are not a target that makes your web browser bad ass. You can pass it one day but not the other for good reason. But what I don’t get is that Safari passed Acid2 in April of 2005. What that person said in that statement (to me) is that they made sure they passed a test they didn’t even understand! Sure if you run Acid2 on the browser on the iPhone it has a little issue but there could be a good reason for it. AND IT DOESN’T MATTER. Web standards are guidelines… just don’t break things and force me to customize my CSS or JS for your browser.

I don’t want to put down the folks at RIM (the value of my house is directly related to their success!), they made some huge improvements. Problem is that they are against a number of new competitors that have years on them with regards to utilizing the web… they need to come across as knowing what they are talking about, even in the local gossip pools.

The team I am on here at U of Waterloo is looking for jQuery or just JavaScript person that is more than just familiar with .NET to give us a hand for a few months (up to 8 months) as we make a big push to get this system ready to go… on time. If you are in the Waterloo area and interested, drop me an email (jrodgers at uwaterloo dot ca). Freelancers are welcome ;)

A twitter conversation got me rethinking about the concept of content vs design yet again. I am constantly in a battle with having to design an interface for content, actions, and requirements that are either contradicting or simply not known yet. That is hugely frustrating however there are ways to design some general things without knowing the specific content and through a few iterations you get there. That is usually what you are forced to do if you are trying to be truly agile.

In Higher ed, what rules is content or design? My feeling is that it is still content. Aside from Alumni and High School students, the gross majority of consumers of information in the higher ed web space are a captive audience. They are staff, students, and faculty that are simply doing their daily activities in a web space they have to use. Sweating over design and what that design should be may not be a fair trade off over just simple content organization. If content is so important I think the use of Microformats is as well because it allows the higher ed space to open up that useful content to a larger audience and potentially enables their internal audiences to use that content better.

Design (impressive, high end, etc) should be more important for micro-sites that are targeting external audiences. An impressive design can be that ‘wow’ factor that will attract those high school students or make your internal audience more comfortable to find information within your web space. However, content may still be more important in the form of a social media foot print in youtube, twitter, facebook, and other places where you don’t have control over design… only the content.

That is not to say good design isn’t needed but I think if you have only 1 day to spend fixing something in your higher ed web space, fix up the content.

As of today I will no longer be President of the University of Waterloo Staff Association. My last act as President was to chair the first half of the Annual General Meeting and then hand over new business to the new President. I take on the role of Past-President that involves co-chairing the Staff Relations Committee and moving to a more advisory role within the Staff Association organization. As President I have two staff that report to me and was in a leadership position. Now I have to step out of the leadership role but stay involved.

In some sense I am happy that my time is up—another kid is on the way and my sanity is getting harder to find!!! A lot was accomplished thanks to the efforts of the UWSA Executive. I can’t thank them enough for the support, the input, the feedback, and the initiatives they brought to the table. Ideas moved quickly and results are starting to show already. One last accomplishment was signing a Memorandum of Agreement between the Staff Association and the University of Waterloo. It was a necessary step that the organization had to do and the Executive made the decision to get it done without a drawn out feedback process from the membership on the basis that that it does not change the working relationship between the University and the employee only the relationship between the two organizations (UWSA and UW). That lack of process didn’t go over well with some in the membership but it was the right thing to do and I am glad we did it.

I have learned a lot about how a higher education institution functions over the past year. Far more than I learned in six years in the Communications and Public Affairs Office and certainly more than I would have an opportunity to in my current role in the IT department. It is a wonder that the organization functions at times but there is a certain value to the organizational structure that is hard not to admire. Now I am part of that structure co-chairing a committee that has oversight over many University Policies that are related to staff.

At the end of my tenure as President the UWSA seems to be getting back to business as usual. A failed union drive offered opportunity and purpose to strengthen the organization and time will tell if that was actually achieved. One remarkable thing that I have learned about the large group of staff in higher ed is that Peter Drucker needs to be required reading for all higher education workers. His management philosophies are applicable to higher education but sadly the execution of any institution wide management strategy is just isn’t there (yet). Another important thing is that some of the best people anywhere dedicate a lot of time and talent to higher education and academics, I would argue, play a lot lesser role in the ensuring higher education works then some would have you believe.

Tonight had to be the most unexpected StartupCampWaterloo yet and it was a load of fun! We had a fairly full room of new faces (60-70) that hadn’t been to a camp event before and really didn’t know what to expect. This left us in a bit of an odd situation as we had no one signed up on the board. So what happened? David Crow made his community pitch to the folks and then everyone introduced themselves as Mic got the names of startups in the room up on the white board.

The number of startups on the white board? 19. There was 19 new startups in the room that were all in fairly early stages. Once all the intros were done and we had a break, a mix of new and some evolved ideas were presented. It was totally not what he had expected for the fourth event but it is exactly what these events should be about. Everything from the project that is being worked on in the basement to a student from Velocity just throwing ideas out there.

The startup community in this town is inspiring.

Do you want to make the system better? Do you want people to use your code? Do you want to work with me? It is close to the end of the first round in co-op here at Waterloo and we have a couple jobs posted. Here is the jobmine info so you can find it easier:

Winter 2009 Co-op 00092349 Software Developer
Winter 2009 Co-op 00092354 Software Developer – Q/A
Winter 2009 Co-op 00092662 User Advocate

We need some passionate students that are keen on web technology to get us to the pilot stage in the spring. Do you think you are up for it?

The technology you get to play with is mostly Microsoft – SQL, .NET, etc – but the GUI likes to use jQuery (before Microsoft decided it was cool).

Just about a year ago I switched jobs on campus from one that focused on applying a broad range of web technology with a marketing and communications focus to a job where I was to focus on user experience of one particular project. I posted some thoughts on what I would have liked to have done in my previous job if I was still there. Have to say, after 12 months I have no idea if any of my list was achieved or even is a big deal to folks that are dealing with U of Waterloo’s web space but it is strangely still important me and I still feel a bit like I need to figure out how to achieve it.

What is truly strange about changing jobs and staying on the main campus is that I don’t really feel like I changed jobs, I just changed projects. Maybe it’s because in my previous job I had a pretty high profile across campus with regards to the web (being the first and only – for a number of years – person hired to work only on the web on campus) and with my current job we are working on a pretty high profile project.

When there was an opportunity for growth presented to me I felt like I had to take it but really wasn’t sure in my decision. However, I have learned a lot that I would not have learned in my previous job which makes the decision to switch jobs a good one a year later. Is my current position better or worse than my previous one? Neither, it’s just different. For me, the motivation to change jobs came from the desire to learn new things and gain from new experiences but there is always a risk in leaving the job you know (or established). I think for a lot of people that work in a large organization and are happy where they are, they can get trapped by the conflict between doing what they know vs the joy of learning something new vs the risk of finding yourself in a bad situation.

In my role as President of Staff Association I have tried to promote changing roles or jobs on campus is a good thing to do both personally and professionally. More needs to be done at Waterloo to encourage folks to move around and I have a feeling in higher education in general a culture of ‘moving around’ doesn’t exist. Given how phd’s don’t change departments… ever… it isn’t a surprise that would influence the culture of higher ed.

For the past few weeks I have slowed into a summer routine of not looking at my watch and just doing whatever comes to mind. It has been a nice pace over last summer where we were flying or driving all over the place and not being home for around 14 weekends in a row.

Besides my obsession with what has been going on in the NFL pre-season or finally being rewarded for attending a CFL game I really haven’t been getting into too much.

I do plan to catch up on stuff this week and get a few posts out… or maybe not. A week into August already and I am just going to enjoy this month ;)

This past week the front-end team that I lead (it includes GUI makers, User Advocates, and UI folks) along with the rest of the team (SOA enablers) are religiously entering a scrum cycle for the remainder of the summer. We have broken into two groups along the lines already mentioned.

The problem I am having is that my group is a mix of the pigs and chickens and I am not entirely sure how to have them all involved. My approach for the moment is to have the UA/UI folks participate as observers in the first 15 min daily with the UI folks really taking the time to go over their tasks from yesterday, for today, and tomorrow. They leave, then the UA/UI folks do their thing for 15 min.

The other challenge as I see it is that we can’t ‘lock in’ tasks for a two week period as the expectation is that clients are giving feedback and expect to see some adjustments on a very short cycle. To address that I have set up two days of ‘respond to feedback’ where we tackle any tasks that can be done in those two days. Anything that can’t fit goes on the list for the next cycle.

This is going to be a bit awkward at first I think… not entirely sure I have it organized properly yet. Hopefully by the next two week cycle I will get it ;) Wondering though, anyone have a similar problem? How do they handle front end development of web applications in a scrum cycle?

Illya posted some thoughts on Agile Release & Testing Procedures and instead of writing a big long comment I figured it was worth a blog post. At the University of Waterloo I have had experience deploying a number of different applications for a variety of audiences… it is next to impossible to get all the details in a post but here is the general truth: there are no enforced institutional wide procedures for web applications. You might think the lack of procedures is bad but it is a result of the relatively low risk environment (even though the campus community has a low tolerance for bugs and changes). There are rarely formal teams of developers, it is mostly the loan coder building a specialty application – enforced procedures would frustrate them.

When you are dealing with a simple web page, say the uni home page, I have essentially covered the typical user acceptance, performance, and stress tests when the page goes live. I go through the gamut of web browser testing, try some OS variations out, and then get it out there. There is a relatively low risk here as the users don’t interact with a database or a whole heck of a lot client side. Once rendering issues are dealt with, it is pretty much unlikely to have other issues. This is with 30 000 or more people seeing it within a short period of time too. I had relative success but I think it was more luck and the fact we kept web pages simple.

Stepping up the development a bit, throw in a Ruby on Rails or PHP application. My testing procedures involved pretty much the same as the web page testing: poke away at it, fix bugs as they appear, and get it ready to go off of the development server to production. We (co-op student and I) never really sat on changes very long. The thinking was that if it went bad on the production end we just roll back the version, fast. When I made the jump to Ruby on Rails development with Capistrano and SVN that became so easy it was scary. On many occasions we had new versions going up two or three times a day. Minor changes, but they add up. This meant a lot of bugs made it out to the community version but as a whole the community appreciated seeing the progress. Our harshest critics were few and usually the type of people that would sit on things until they are perfect, the web is never perfect.

Now I find myself in the .NET/C# development world. I am happily hacking away at the JavaScript on the front end but I still live in the development environment. Here we have a solid team, a lot of developers, some serious tools, and totally different requirements from the client relationship/expectations end. At the moment we are doing limited testing that makes sure it works and then pushing it to an environment that a group has a ‘sanity check’ and gives us feedback. Releases are going out on a weekly build routine with a daily routine for an internal release. The whole process is evolving as we go but in a very general sense we are aiming to maintain a weekly build schedule for one set of users, daily internally. Our goal is to not leave the application in a non-working state and at any time the build could go live. This habit takes time to develop though… I don’t expect us to be in the groove until over the summer.

That is the nutshell version of what I have had experience with, I suppose it is Agile without the buzz terms. Personally I don’t see a reason why any web application couldn’t work on a daily build process. If you break the big change down to a lot of little changes you reduce the risk of breaking it and you ensure stability (so the theory goes). The problem is that in order to break a big thing down to a bunch of little things you need to take the time to talk it out, plan it out, and scope out what goes into a big thing. It is a way of thinking and it doesn’t happen overnight, most people need experience thinking that way.

I am interested to know what other higher education folks are doing with release and testing procedures.

With our second StartupCampWaterloo behind us here in Waterloo we hit a milestone. Over 100 people were in the main area of the Waterloo Accelerator Centre to talk with Startups and help each other with ideas (quick estimate based on 88 chairs in the room plus Ali’s colourful chairs). I am pretty sure all those that demo’d got some useful information and experience out of the evening.

A big thanks to Stefanus De Toit for opening up the evening and breaking-in the crowed by sharing insights like: Turning academic research into a product is hard if you don’t keep your paperwork in order; hire your friends; wow people with lots of 3D chickens to get investment (actually prove your concept with a solid demo). Another big thanks to Austin Hill for closing off the evening with a great presentation which included: don’t be afraid of sharing your ideas because someone already tried it – it is your execution that is important; Canada needs more of its successful entrepreneurs re-investing in the startup scene; beware the vulture investors; do a startup while you are a student; it helps to work for a startup if you are thinking about a startup as startup culture is infectious.

What was learned from this one is that 60 second intros with voting works out really well. Keeping things short and keeping the slides out of it kept the conversation interesting and focused. The big buzzer also helped. Only took one person being caught by it—no one else dared challenge their time limits. Plus it kept us on time, mostly.

I had a lot of good feedback and now can relax—until the next one. What are we going to do next? BarCampWaterloo is on March 29th, a DemoCampGuelph will be in April, and StartupCampWaterloo3 will be sometime in May. If you can’t figure out if you want to go, I have a post coming up tomorrow that will cover that ;)

Other folks to thank for making the trip from places afar and/or helping out last night… The Toronto folks venturing outside of the GTA in their large 4×4: David Crow – thanks for the books and disruption, Jevon McDonald,  Jonas Brandon.   Ali Asaria brought some chairs and name tags and Simon Law for came down from Montreal. The other organizers Simon Woodside and Mic Berman ensured that we appeared as unconference as possible ;)

Most importantly, the night was good because of the folks that were there. Waterloo has a great community.

It is interview time here at Waterloo. It happens once every four months, thousands of students and employers enter a dating game for talent and experience. Waterloo is a bit unique having a building dedicated to the process (just happens to be where my office is) and a frequency of three times a year for the process to run. Large companies like Google, RIM and Microsoft are hear hiring large numbers of students but so are local startups like AideRSS and Semacode along with all sorts of companies from different fields and different sizes. Posters on the walls with all the different information sessions show all the opportunities for students.

Why do the companies come here? Waterloo has the talent and I would argue there is far more and better talent than Stanford (update: Larry disagrees or does he?). Our students go to the Valley or Seattle or Boston or Ottawa and all points in-between to work for big names and get started on their carriers while they are working on their undergrad (or grad) degrees. A lot them stay local (Google and RIM are in Waterloo, along with a lot of other interesting employers) and even more would like to stay local for a term or two if a great job can be found.

For local web/tech startups this is a great opportunity. If you developing an idea and you need someone that can code and wants to contribute, for around 10K you can get a junior student for four months to do that. Senior students are more but you get higher quality and more experience. Just to prove a startup concept though, a junior co-op student is inexpensive and hugely beneficial.

The project I am working on depends on the quality of Waterloo Co-ops. We are building a new system to run the job/dating game and have a great bunch of students to do that. They code, they ask questions, they learn, they are excited, and they build really cool things from your ideas. Over the years I have worked with a number of different students and all of them made me look good—which is what you want when you hire someone, right? ;)

There is a side benefit to local startups hiring students I think as well. If you keep the students here, keep them engaged, and get them excited about trying out their ideas you help the local community build resources. I think it’s one part of the puzzle that may help Waterloo’s stealthy startup scene become even more open and exciting.

If you are wondering how to hire a co-op, contact CECS and they will have you set up in no time.

In my relative short career I have not had the pleasure of surviving a unionised environment except as a summer student doing landscaping work for the City of Sault Ste Marie. IT related work environments just don’t seem all that interested in a union, I would argue most knowledge workers have little interest in such a club. However here we are in 2008 at the University of Waterloo facing a vote in an attempt to certify OSSTF as a bargaining unit on campus. The vote is today however the outcome won’t be decide for approximately a month due to some dissagreement in who is in the bargaining unit.

The one thing that does get me about this entire process is how the law in this province favours unions over the individual. Maybe in industrial work environments the method used to unionize makes sense as workers generally may be easily replaced and can be easily bullied. However in a professional work environment, where it can take a few months to a few years before a worker performs at top form with higher education credentials, it feels like the whole process tramples on your rights no matter which side of the fence you sit. The behaviour out of the union itself just feels like they are after members, they don’t actually care about the workers otherwise they wouldn’t pursue unionization where the support is 50-50 at best (here it is 60% against, but they need to vote).

This whole experience has taught me a lot and I’d like to think I managed to get through it, up to this point, as President of the Staff Association (the opposing force) with only being called a few names: Meat puppet, lap dog, etc. Oh and apparently I have been paying people to vote… that would mean I had personal wealth large enough to do that. Cool, someone tell my bank manager ;)

Over the past year or so the MMNP effort has been working on ways to utilize mobile and media based technology on campus. A year ago a pilot project looked at the possibility of students replacing their land lines in residence is relatively smart phones. Lots was learned (primarily that students are shell shocked by the telco cost and don’t really use them even when a large chunk of costs are covered) and the project moved on to different ideas. One of those ideas was a living environment that doubles as an incubator for entrepreneurial students.

Enter 2008 and the announcement of VeloCity. The Daily Bulletin article covers all the details. From the VeloCity site:

“It’s a place where some of UW’s most talented, entrepreneurial, creative and technologically savvy students will be united under one roof to work on the future of mobile communications, web and new media.”

I was involved with the project early on and it is great to see that Sean has taken his idea and made it a reality. I expect to see some exciting things come from this housing experiment. What a great opportunity for some students!