Some of my favorite movie characters are serious dummies. Carl from Caddyshack, Lloyd from Dumb and Dumber, Brick from Anchorman. I love them because they’re funny but also because I can kind of relate to their struggle.
I mean, to be fair, I’m not actually THAT dumb. I don’t eat candles or love lamps, but let’s just say that in an office full of smart people, nobody is asking me to code or develop anything. Pipelines and proposals are where I spend most of my days.
So recently when I was asked to build out a OneCampus site, I was pretty sure I was being pranked. Either that or they asked me to do it as some sort of social experiment to see what happens when you ask an administrative person to do something “technical.” Nevertheless, with enthusiasm in my heart, I accepted this new project and considered it an opportunity to become…less dumb.
Recognizing that OneCampus was designed to require very little IT lift, I knew there was hope for me right from the start! But, the big question was how was I going to get there?
Having seen several schools go-live over the past several months, I decided to look at the project as if I was a customer. First, I did a bit of brainstorming and identified the key components of OneCampus including:
- Roles: The groups or types of users that will access OneCampus (e.g., student, staff, faculty, parent).
- Markets/Campuses: A way of organizing tasks that relate to specific campus sites or departments.
- Categories: Allow you to bucket tasks for easy browsing, if desired.
- Contacts: The person or department responsible for questions/concerns about a specific task.
- Tasks: The descriptive tiles that provide info and direct links to the various services available on campus.
- Task Centers: A collection of related tasks. For example, all items related to Freshman Orientation.
- Tags: Additional keywords or commonly used terms that will aid with search.
After some careful consideration, here is what I ended up doing, in 3 easy steps:
- I started by mapping out which roles, markets, categories and contacts made sense. Then I created those as a first step.
- Next, I used a Google Spreadsheet to organize my tasks by category, wrote a description for each, and filled in the key fields such as tags and contacts. I also considered what icons I might use for each and determined which tasks could be bundled into groups (task centers).
- Finally, I used the content in the spreadsheet to build out the individual tasks in about 3 minutes each.
In the end, I created 68 tasks that I bundled into 9 task centers. OneCampus is very intuitive so the process was incredibly easy. When I had questions, I was able to find answers in the quick guides. The project took me about three weeks to complete from start to finish. Not too shabby for a non-technical person who was working on a variety of other things at the same time!
If your institution is considering an implementation of OneCampus you might be asking yourself questions like, “How many people will need to manage this?” or “How long is the setup going to take?” Let me just say that if someone like me can do it, by myself, in a matter of weeks, just imagine what you will be able to do!
To learn more about how easy it is to get started with rSmart OneCampus, visit our website at www.rsmart.com or call us at 866.874.4338 to schedule a demo today!
About the Author
When Jennifer Martinez isn’t managing rSmart’s sales support activities, she enjoys spending time with her husband, two children, and rescue dog named Diesel.