UFIO Platform Spun Up and Launched!

My goal last month was to have the UFIO platform and Financial Services site launched by the end of April. Well, I beat that deadline by over a month, launching both sites March 27. The directory of UFIO still needs some finessing, but it’s in great shape and we’re looking forward to moving on to Facilities Services.

Financial Services Site Live

Work was speedy with Financial Services and we got the site content into shape in about two weeks.

Project Communications Newsletter on Target

I have written an article about the Steam Tunnel project as well as an update on the OFSC panel failure. I’m working on getting the newsletter template finished, using a brand template from URM.  I will run the communication by URM/Steve Clark’s office before sending, and work to create an editorial calendar for the next few months.

Upcoming in April

  • Attend AEA Seattle
  • Launch Project Communications Newsletter (Campus Directions?)
  • Create content/get Facilities Drupal site into shape. There is some customization for the Facilities Services site so I am not keen on setting a launch date yet.

UFIO Development Site

The biggest achievement for the month of February was getting approval on a separate website instance for UFIO, also receiving approval from the domain name committee, and getting the development site for UFIO spun up.

Next steps for this will be to build out the new UFIO site, using Financial Services as a model. There are site-wide features to build out, such as Views, Paragraph Bundles and Blocks and I will need help from Web and Mobile Services for this. My goal is to have the main UFIO site and Financial Services site completed and rolled out by the end of April. The UFIO site will be a mirror of the current site, so it’s mainly a copy/paste and redirect job.

After this sites, the plan is to migrate in this order:

  1. Facilities Services
  2. Leasing
  3. GIS/OSu Maps Library
  4. Others (develop plan)

Project Communications

During the week of Feb 12, I ran a Project Communications survey in OSUToday and distributed it to a few closed communication channels I belong to. The purpose of the survey was to identify capital project communication needs and wants among the campus community. Results can be found at the newly revived communication blog, Capital Project Updates on Campus (formerly Capital Construction Updates). Ideas for a catchier name are welcome and appreciated 🙂 I plan to distribute a Project Communication plan and calendar for 2018 at the next Leadership Team meeting.

In addition, working with the Project Controls Manager a form for Requesting Minor Capital Improvements was created and approved.

Space Management

In early February I met with the Space Management team to discuss their needs. The bounce rate on the Space Request form is quite high (60%), so I recommended a shorter space form. I created the form and sent it to the Space team for review, as well as starting to review higher traffic pages for flow/reduction in content.

An Event Apart finished strong with three good sessions. I hope that I get to attend next year!

Unified Design – Cameron Moll

We need to work around to a unified experience around screens. Previous experiences inform new experiences.

The best interface is the one within reach, but 49% of users email themselves a link to continue using the content later.

RWD ends where the browser ends – the spirit of RWD but unified all technologies – Unified Design. This is the next frontier of building sites – a consistent experience regardless of where or what device the user is using.

77% of searches on mobile are at work or at home (where one assumes there is a desktop nearby).

Screens and interfaces are converging and your audiences are looking for unified experiences.Example: People want to use Lightroom on the phone – but it’s very resource heavy. But users get frustrated expecting Lightroom to work the same way it’s worked before, on desktop.

Unified Design is the next frontier, building on RWD – a consistent experience regardless of where/what device the user is using.

Design has told us that form and function is most important – function is becoming way more important than form.

The concept of data symmetry – same data across items because 40% of online users start activity on one device and finish on another.

Slack – a great example of a cohesive experience across devices.

Best practices that foster unity:

  • Unify internet presence #unityfirst – design the core experience first.
  • Treat every facet of the user experience as a contribution to the experience.
  • Moving towards an duocratic branding experience (user decides).
  • Consider web views for native apps – web vs native is mattering less and less.
  • Unify actions, not devices.
  • Store data in the cloud, not locally (amazon cart)
  • Language choices starting to matter – replace the term “click” with select or point.
  • Replace the term mobile (which ppl tend to think as iphone) with small, smallish. Think beyond the phone/ipad/desktop dichotomy.
  • Eliminate big screen bloat.

Compassionate Design – Eric Meyer

Build for humans, not users or consumers.

Autotagging can go awry – put terrible tags on photos that people can not even be aware of.

Project pre-mortem – a meeting where discussions are happening about the worst outcome that can happen. How things can fail. A person serves as a dissenter – identify assumptions and subverts them. Everyone gets a turn as this dissenter, practice deep thinking.

If we’re going to do this *feature*, how can we do this ethically?

Instead of edge case, consider a “stress case”

It’s important to Signal Intent

  • Google should have signal intent with mic drop feature.
  • Explain what we are asking and why we are asking it.

You have to go off brand to be a human and be compassionate sometimes.

Clarifying intent behind questions: The Question Protocol.

  • Who is going to use this info and why?
  • What are we going to do with it?

Making the case for compassion in your work

Be conservative with what you send and liberal with what you select. Compassion can help you make money, save money and decrease risk. Compassion is hard – takes courage, willingness to accept users how they are.

Empathy with our users is courtesy. Compassion is vital.

Designing for Performance – Lara Hogan

My brain sort of checked out at the end of the conference and I didn’t take the greatest notes for Lara’s talk, unfortunately.

A cellular device must establish a radio channel before sending and receiving data. In this speed, mobile devices are roughly analogous to dialup.

Image file size tips –

Blur background to reduce file size, because jpgs don’t handle edges that well.

Image sprites – a bunch of images in one file.

Old IE downloads all @font-face files, so only import font weights you need.

3d Firefox add on to visualize page depth – Tilt 3D (I couldn’t get it to work).

Make performance part of everyone’s workflow.


oregonstate.edu over a cable connection. Site is usable at 2 seconds.

Resilience: Building a Robust Web that Lasts – Jeremy Keith

Lots of history of the DARPANET and ARPANET and Sir Tim Berners-Lee. I wrote a paper about this in grad school so it’s all sort of review for me, so I didn’t take any notes. I did enjoy, however, seeing Sir Tim’s paper about dealing with information management (aka the www), complete with notes from his supervisor:

from: http://blogs.bournemouth.ac.uk/research/2014/05/28/the-case-for-open-access-within-a-university/
from: http://blogs.bournemouth.ac.uk/research/2014/05/28/the-case-for-open-access-within-a-university/

html – originally 21 elements

html5 – now 121 elements. How do you add 100 elements to something and it still works?

Because browsers just ignore the elements that they can’t render – they’ll ignore the tags but still show the content. This is a declarative, more resilient tool.

Compare this with Javascript, a more fragile, imperative tool.

html works well on the web because of the web’s inherent variability. We don’t know and can’t predict what browsers, interfaces networks, & user situations will look like in the future.

What we can do, going forward:

  1. Identify core functionality of a site (i.e. help users complete a task)
  2. Make functionality available with simplest technology
  3. Enhance Enhance Enhance

examples: Provide news (any newspaper), send messages (Twitter), send images (Instagram).

A sad state of affairs – nasa.gov requires 3mb of javascript just to render text.

Adapting to Input – Jason Grigsby

Four truths about input

  1. Input is exploding – voice control, fingerprint sensors, etc etc.
  2. Input is a continuum – we’re device bending = and can no longer make assumptions based on screen size.
  3. Input is undetectable – we can’t tell within a browser what a user is going to do to input. Only can tell after the fact.
  4. Input is transient – just because I do one thing doesn’t mean I will do it again.

We need to adapt to input

  • Design to the largest audience, by default
  • Build it accessible – makes it easier for newer technologies to be adopted. See being resilient on the web!
  • Design for multiple concurrent inputs because inputs aren’t binary. And…be more input agnostic in vocabulary.

***It’s time to retire “click here”**** We’re entering the era of pointer events – abstract contact with inputs.

Progressively enhance inputs – do the new cool stuff. Warby parker using the gyroscope, beacons instead of apps to control stuff in the future.

Make inputs part of your test plan. Your testing lab is the local Apple, AT & T and Verizon store.

Unfortunately, I had to miss Designing Meaningful Animation. 

I was bursting with excitement because…Gerry McGovern! I am inspired by his work and his singular focus on solving user’s problems and identifying user tasks. I am the living heart eye emoji when it comes to him.

Top Task Management: Making it Easier to Prioritize – Gerry McGovern

How can we get the information to you as soon as possible Google is about solving problems for you.
i.e. search results – to the info shown IN search results – to the info showing up in the URL.

When you understand the task the speed and expectation becomes faster.

Interesting test results – whichtestwon.com

Smart people sitting in a room – worst way to design a website. There is a huge difference between looking at and using a website. Preferring vs using – a gut instinct isn’t good to listen to.

***Tiny traffic is where the ego lies in an organization*** As if most people care what an organization says about itself. All this tiny traffic garbage damages users getting to actual tasks.

Organizations are really good at getting in the way of people doing what they need.

The most skill we can have is understanding our customer’s needs. Move away from ego towards empathy.

Marketing is like antibiotics; we’re becoming immune to it. More cynical to messages. Brand value is in decline and customer value is rising fast. Consumers and users are less and less trusting of messages.

Intangible assets

  • customer base, intelligence
  • trust moving away from orgs, moving towards friends and me.

Identify those tasks

  • Top 50 search terms
  • To 50 pages, files (PDFs count too!)
  • Trad. media
  • Emails – what are your customers emailing you about?

Discover the user ecosystem, instead of yours.

Web teams must manage the tasks – outcomes as well as components. When identifying tasks, teams must establish target times for completion.

Constantly improving and iterating – digital is never static. Always measure your tasks and environment.The distance between users and org is farthest in digital, and most crucial to understand.

The Physical Interface – Josh Clark

from http://omershapira.com/blog/2014/09/its-raining-again/
from http://omershapira.com/blog/2014/09/its-raining-again/

Interfaces are requiring us to be more robotics instead of interfaces being more human.

Interest lies in the mundane technologies (like auto car windows), them becoming:

  • cheap
  • functional
  • accessible

The best interfaces translate intent into action. Mobile gives computing power to immobile devices through bluetooth – everything can be a sensor (diapers, asthma inhalers..)

What if a physical store could do what a online store does? Amazon’s physical store is the start of this. You could touch the product for more info, walk out of the store to buy it (just like Food Innovation Center’s RFID project!)

Where is the universal connector network? The physical web, broadcasting its interface -> like broadcasting a URL. (we could do this for user test screening!)

Objects should speak only when there are important things to say – goal is not to make things talk but to improve the conversation.

We’re moving into surveillance capitalism – at what point are we no longer controlling objects and are being controlled by them (ie. Siri teaching us to say names in a weird way). Our values amplify our humanity.

The Ethical Design Manifesto – check that they values of your creation bend to your lives.

ana event apart seattle day 1

Hello from Day 1 at An Event Apart Seattle. We got lunchboxes as swag – my kid will be thrilled.

Designing with Web Standards – Jeffery Zeldman

He started out the talk describing problems we are all facing – 1000s of devices, folds and feeling like a fraud and insecure because he can’t keep up with code, the new tools and the new things to do.

Do we need CSS? We can do it all in a JS framework! But scripts fail.
Bloat then – Dw
Bloat now – Bootstrap (“Using MS Word to send a text message”). Bootstrap’s a great way to prototype, not good for production code.

Modern web standards bible- Adaptive web design by Aaron Gustafson

Your brand happens between devices. CSS flexbox makes it easier to separate layout from presentation.

The people writing the CSS need to be talking to each other

  • Make style guide
  • Hire a code design director.

Rules for designing with web standards:

  • Content & structure 1st
  • Remove distraction. Design is 90% typography and 90% whitespace
  • Design system to serve content
  • Style is servant to brand and content
  • Speed is very important
  • Design to make user clever.

Designing Deliberately – Yesenia Perez-Cruz

Some of my really sharp coworkers have been talking to me about performance for over a year. Now I really get it.

Performance is a design feature. Prioritize performance from the beginning.

Beauty and usability are in balance. The goal is to deliver core content quickly, by being deliberate with design choices.

Three stages of the design: Core > Enhancements > Leftovers

A user’s perception of when the content was usable (readable) is more important than actual load time.

Ways to make performance a priority…

  1. Make performance a project goal. Good for users (keeps em happy and coming back) which is good for business.
  2. Set a performance budget – a tangible way to talk about speed. Every design choice has consequences. “That carousel will cost you 700kb”. Performance budget builder
    1. Videos are great for showing speed.
    2. Webpagetest.org
    3. For every design decision, we must ask – what value does this choice provide?
    4. When performance guides design decisions, decisions are made less arbitrarily.
  3. Performance budgets help us design deliberately. Web fonts are overused and that comes at a cost. Do you really need web fonts for smaller screens?

Consistency does NOT have to mean identical – a singular design expression, never uniform or static.

The bad part about brand guidelines are that they can be too rigid – time to think about brands in more flexible ways.

A new web strategy – Start with clean experience, then layer on brand experience.

Designing modularity is a precursor to style guides. Identify reusable patterns and use only what you need. Think modularity to differentiate just enough.

cssstats.com – How many styles do we have?

Oregon State University: 34 unique colors, 53 unique background colors (total redundancies here), 12 font families, 33 font sizes (!!!)

Real Art Direction on the Web – Jen Simmons

I probably understood this session the least, but I understood enough to get excited about some of the possibilities!

Bootstrap and 960 Grid system is the reason that websites all look the same today. Turned web layouts into a multiple choice question.

Break away from that –

  • Use negative space as a way to guide the eyes. Communicate using space. Create an oasis.
  • Get off the grid design.
  • Use odd number instead of even number of columns – gives you a different look.
  • Give the users with the latest browsers great experiences – don’t kidnap everyone and hold them in IE 8-land.


Viewport units – sizing things relative to the viewport size

Object-fit – controls the size of the box and adjusts the aspect ratio of the units.

Css-shapes – breaking out of squares to flow texts around objects. CSS Shapes editor (for Chrome) does the math for you.

Clip-path – breaking out of squares and rectangles.

Css-round – can’t really be used yet (browsers aren’t supporting). Using polar positioning to determine angle and distance.

Book: Just Enough Research by Erika Hall, published by A Book Apart.

Chapter 1

(Begins with lots of explanation of basic vs. applied vs. design research)

In design research, context is everything. Better you know the current state of things, the better you will be positioned to innovate.

User centered design:

  • Expose patterns in human behavior
  • Explore reactions
  • Shed light on the unknown.

Design research requires us to approach familiar things as if they were unknown to see clearly.

Research is not asking people what they like. Like is not part of a critical thinker’s vocab. It’s a superficial and self reported mental state.

Chapter 2

Involve people (espec. higher ups) in the research so they’ll be more likely to adopt changes.

It’s more fun to be the smart person with the insights than be told what to do by the smart person.

Doing research together makes the team more collaborative:

  • Someone needs to be the lead – keeping things on track, responsibility for the work.
  • Everybody needs to know:
    1. Purpose of research
    2. Goal “”
    3. Their role
    4. Process

Include research activities that support specific decisions we anticipate.

Begin with Generative Research – finding out what the problem is
“What’s up with the…?”

  • look at questions on social media
  • interviews
  • following people around

Next, tackle Descriptive Research – the best way to solve the problem we’ve identified
“What and how…?”

Then, Evaluative Research
“Are we getting close?”

  • Define potential solutions
  • Testing solutions – A/B testing, usability

Also, Casual Research – identify possible cause and effect relationships
“Why is this happening?”

For each project, clear identification of roles – assign them at the outset!

  • Author – plans and writes study
  • Interviewer/moderator – interacts w participants
  • Coordinator/scheduler – schedules w participants
  • Notetaker/recorder – not interviewer!
  • Recruiter –  screens participants
  • Analyst – analyzes data, looks for patterns
  • Documenter – reports findings
  • Observer – a good role for higher-ups! Can watch raw footage.

Being a responsible researcher means noting your bias

  • Design – are you biased on how the test is structured?
  • Sampling – is your sample biased?
  • Interviewer
  • Sponsor – softening results to client.
  • Social desirability – looking good to client

Research rigor- best practices

  • Phrase questions well
  • Set realistic expectations upfront
  • Be prepared
  • allow enough time to analyze
  • Take notes about EvEryThing!

Your email dings and you look up, heart sinking as you see the words “Add to website?” in the subject line. You open the email and scan the attachment, seeing 15 photos of people with their backs to the camera, standing in a field somewhere, looking at an unidentified small plant. Or people in a classroom doing…stuff?

Fascinating image
Tell me more!












The event details and photos are not exciting, they don’t align with your content strategy, and they don’t further your unit’s goals or users’ goals at all. But the person emailing you is faculty, or an adviser, or someone you want to keep a good working relationship with. But you do not, I MEAN DO NOT, want this content on your website.

What to do?

I’ve found it helpful to keep a list of tactics, deflections, and strategies designed to help you push back, and find a more appropriate place for this content.

For your allies (people who understand that you are more than just a webmaster):

  1. Ask them how this content serves site’s criteria for audience, goals, or message. I’ve found that it’s helpful to have a one or two sentence description of these topics so that you can refer to them quickly/copy & paste into an email.

For all others:

  1. Social Media – because I am not a social media manager, this is a really easy tactic for me to apply. YMMV. Content shared in social media will dilute the message and may reduce engagement. However, it will most likely “disappear” and not be a problem in a short amount of time.
  2. Email – If this is content that would be appropriate for a limited audience, send it through email.
  3. Archive – If the photos are good, high quality photos that could (in theory) be used in different ways, add it to an (off line) photo archive for future promotion.

What do you do when you are told to “put it on the website”?

Hey there!

The CAS Web Team will be holding open office hours this Thursday, February 11 from 2-4 pm.

Please stop by Strand 200 or call us at 7-5641. We’re here to answer (or direct) your agsci.oregonstate.edu Drupal or WordPress questions or talk about any content questions/plans you may have!

We hope to see you.

(I am talking about the visual brand – the voice & tone is another issue entirely) 

I spend a lot of time convincing people as to the importance of following Oregon State’s brand identity guidelines. I’m a true follower-if for no reason other than I am lazy and want the way-more-talented designers and site builders do the work for me.

But also I believe every good site we publish that adheres to our guidelines is a chance for us to deliver on our brand promise, and amplify the awesome work that Oregon State does. That doesn’t mean, however, that I am not thrown for a loop when faculty, staff, or students argue with me that they can’t possibly follow the branding guidelines for very important reasons.

I thought I’d list the most common arguments that I hear and how I respond to them. I’d like this to be a useful post for all web workers on campus, so let me know if you have faced arguments and how you encourage and convince people to follow our brand identity.

Most common argument: “But it’s boring!” usually followed by showing me something terrible for accessibility with Javascript rollovers and the like.

Counter with:

  • The content is what’s important on a site and what needs to set the site apart. Not boring content equals a not boring site.
  • That “cool” feature is actually not accessible to anyone using a screen reader, with visual difficulties, etc. Our OSU-branded websites have been evaluated for accessibility! Direct them to the Web Accessibility guidelines.
  • Following the branding guidelines means fewer decisions about design, color, and placement.

Argument: “But I don’t want it to look like an OSU site for reasons!” 

Counter with:

  • Are you using OSU resources, money, or people? Then it stands to reason that the website should be an OSU-branded property. (This occasionally backfires if it’s a joint research project. See Co-branding guidelines for more details.)
  • Using a OSU branded website instantly communicates to your stakeholders that this is an authoritative, official website. Provides credibility and authority that your name may not deliver.

Argument: “Why is this important? Why do you keep talking about it, come on!”

Counter with:

  • This website needs to uphold OSU reputation and promise to its stakeholders. One way of doing this is branding it correctly.
  • Our unified look allows us to speak with one powerful voice – across Oregon, the US and beyond.
  • Every website we create is another opportunity for us to emphasize what OSU stands for and what makes OSU special. Let’s do it!

Final Argument: “Ok well….I’m still going to do this awesome onmouseover event that breaks everything.”

Counter with: “As an employee of Oregon State, I follow branding guidelines. I will be unable to help you create this site.”

It is so, so hard to draw the hard line, but 9 times out of ten they’ll back down and realize that if they want help, brand guidelines it is!

What arguments have you used?