What’s in a name? (Part one…)

RNC Logo blackBack in 2005, when we first started the little idea that has become this behemoth, the event was called the Revit National Congress. We didn’t have a long-term goal for what the event would become, or who it might reach, or even how the process might be managed. Instead, we simply had thought, “this will be cool, we can do this” (talk about throwing yourself into the bearpit!). People had a great time at that ‘Congress’ and immediately wanted to know about the plans for the next one.

Ummm, what?

Ok, we need to make some plans, fast! It was really only at this point that we started thinking about some of the longer-term implications of how we plan and implement. Almost right away we realised that ‘Revit National Congress’ was quite a limiting name.

Why? Well, even 12 years ago we recognised that the word ‘Congress’ might have some negative connotations associated with it (and this was long before we considered a North American event). Equally, while we really had no plans for international expansion, calling it ‘National’ just seemed to be unnaturally restrictive. So, by only our second event, we had changed the name of the event to the Revit Technology Conference, and there it sat for 9 years and over 30 events.

Oh, and hey, for those of you who have been tracking such things, you’ll notice that my geographic dysphasia was an issue right from day one… the event was held in the Blue Mountains, an hour and a half west of Sydney!

Fast forward to 2010 and planning was well underway for our first RTC event outside of Australia (2011 Huntington Beach, in California, USA – the first New Zealand RTC didn’t come along until 2013), and suddenly the question of region specification raised its’ head. We knew that our event here encompassed the New Zealand community, that any event in the United States would pick up the Canadian community, and that we wanted to overtly include those people. We already had an active intent to ensure the events made it onto those ‘foreign shores’. So the US event became the first event as part of RTC North America, and the events in Australia became RTC Australasia.

Geographically and demographically precise, occasionally incomprehensible definition… Australasia is a term that denotes Australia, New Zealand, New Guinea and some of the small neighbouring island nations. Sounds good (I don’t think we will ever run an RTC in New Guinea, but Fiji or Tahiti doesn’t sound too bad….), but the reality is most people aren’t aware of the definition of the term and so all it ends up being for them is confusing.

Fast forward another few years… It’s 2015 and we’ve just held our first Asian region event, in Singapore. Now we have an Asian and Australasian region. Ok, that’s not clear and simple. Also, we have now had an RTC in New Zealand, and it is also really clear that a small island event doesn’t make sense.


It’s time for another name change! RTC Australasia will henceforth be known as RTC ANZ (that’s a reference to Australia and New Zealand, if you’re not from around here).

This better reflects the Australia / New Zealand primacy of the communities that this event actually serves, removes the ambiguity of the definition of the region name, and also will prevent confusion of the events between ANZ and Asia. Hey, and it’s shorter (Australians love to shorten everything)!

The events themselves have of course not changed. Whether you attend a single event, in a single region, or 9 events across 4 regions, you will always get the passion, energy, and care that characterises an RTC event. The only change you need to watch for is how it is displayed and managed in social media. Historically we have used the hashtag #RTCaus for the local events but now we would like you to use #RTCanz instead. At the same time, the hashtag @RTCevents has become the default twitter account for all posts related to RTC (as opposed to Data Day, BCS and the Design Technology Workshop). Please follow @RTCEvents for information related to all events, and then also hashtag the local event (#RTCanz in this case) when referencing the specific event.

Do stay tuned for some announcements in a similar vein to this one….

Translate »