Do you think that Congress represents your interests?

How you answer that question is probably going to depend on your outlook, ideology, and social position.

But as Congress is increasingly dominated by the wealthiest Americans, and out-of-touch ones at that, Americans are rapidly losing faith in our political system.

Then add to the recipe, the Supreme Court’s 2010 decision in the Citizens United case that opened the floodgates for unlimited corporate and union Super PAC spending.

Now the Supremes are are at it again.

On Wednesday the Supreme Court ruled on a campaign finance case called McCutcheon v. FEC. Here an Alabama businessman and political activist was challenging a federal law that limits the aggregate individual donations of a citizen during an election cycle. His claim was that this was a violation of his First Amendment’s free speech protections.

Before the ruling, federal law barred any individual from contributing more than $123,200 to candidates and party committees during an election cycle.

That limit has been thrown out by the court, although there is still a limit ($2600) on what an individual can give to a single candidate.

The decision, penned by Chief Justice John Roberts, depended on the idea that removing limits for wealthy donors doesn’t create “quid pro quo corruption” or its appearance.

In Chief Justice Roberts’ words:

Spending large sums of money in connection with elections, but not in connection with an effort to control the exercise of an officeholder’s official duties, does not give rise to such quid pro quo corruption. Nor does the possibility that an individual who spends large sums may garner “influence over or access to” elected officials or political parties.

Do you agree? Do members of Congress favor the interests of their wealthy donors, and is that corrupt?

Should the government regulate political contributions at all? 

Feel free to leave a comment about your thoughts on the issue. But remember, since money is speech, the richest commenter wins.

Three students in UMBC’s College of Engineering and Information Technology (COEIT) Department of Computer Science and Electrical Engineering (CSEE) have been selected for major scholarships to pursue studies in cybersecurity-related fields under UMBC’s participation in the National Science Foundation’s (NSF) Scholarship for Service (SFS) Federal CyberCorps program. As SFS Scholars, students receive full tuition, fees, annual reimbursement of professional development expenses ($3,000), a nine-month stipend ($20,000 for undergraduates, $25,000 for MS/MPS students, and $30,000 for PhD students) for up to two years (three years for PhD or BS/MS), and assistance with federal cybersecurity internships and career placement. To be eligible for SFS funding, applicants must be full-time students at UMBC committed to cybersecurity-related research and education activities, have an excellent academic record, and not have any significant outside employment obligations.

The first-round awardees for AY14-15 are:

• Anastasia Raffucci, BS (CMPE)
• Jackson Schmandt, Ph.D. (CMPE)
• Brooke Young, BS (CMSC)

These new awardees will join existing UMBC SFS Scholars Oliver Kubik (BS, CMSC), Mary Mathews (PhD, CMSC), Nathan Price, MS (CMPE). Punlada Muangrat BS (IS), Alex Cooke BS (IS), and Denis Danilin MS (IS).

ADDITIONAL SLOTS AVAILABLE! Applications for SFS support for AY14-15 will be accepted through 12PM (noon) on Friday, May 2, 2014 with notice of awards made by May 23, 2014. All levels of study are welcome to apply — however, students must be admitted to (or already enrolled at) UMBC first before applying for SFS. For information about SFS (including application information and instructions) and other US government-related cybersecurity scholarships available, please visit the CISA website.

The CyberCorps program produces highly-qualified professionals to meet the United States government’s increasing need to protect American’s cyber infrastructure. While in the program at UMBC, SFS CyberCorps Scholars participate in special SFS program activities, have opportunities to engage in mentored research opportunities both at UMBC and its partners from industry and government, and must complete a paid summer internship for the federal government. Upon graduation, each student must work for the government (for pay) for one year for each year of scholarship received. CSEE Drs. Alan Sherman and Richard Forno direct the program under a five-year $2.5 million NSF grant received in 2012.

Join us for the 18th Annual Undergraduate Research and Creative Achievement Day on Wednesday, April 23, 2014. Meet alumni Corey Fleischer, winner of Discovery Channel’s “Big Brain Theory” competition. Over 200 student presentations from all disciplines!

Visit the URCAD website for more information.

A lot of mobile-minded talented folks across the globe produce great work, but yet sometimes you still hear many of them complain about their relationships with their clients. They often mention feeling isolated and not truly understanding what the client really needed.

This lack of personal interaction often leads to misunderstanding, as well as less awareness of and appreciation for all your hard work. While involving clients in your mobile workflow can be challenging, really working together will make a big difference. In this article, I’ll share some important things I’ve learned about involving clients in my mobile workflow. Let’s dive into some tips and tricks that I use every day.

Work Out Your Manifesto

Projects don’t happen overnight. It usually takes a few meetings to get to know the client and to discuss collaboration. Your company’s business strategists and account managers invest a lot of time and energy in this process. While they will often seem to distance themselves from your daily work, speaking with them is a real window of opportunity. These “suits” are the first ones to meet potential clients, and they convey your company’s vision, portfolio and creative approach. They can be a great help in nurturing a more involved relationship.

A great way to approach this internal conversation is to work out a manifesto, a summary of your creative vision and beliefs. Get together with your team and discuss your existing workflow and how it could further support what you really stand for as a team. Ask the team lead to help you work it out and make the message tangible. Do this simply by making a presentation to your colleagues. But why stop there? You could design posters, flyers, even stickers for your team so that they can help you spread the word.

“Design is not an afterthought,” from Little Miss Robot’s manifesto. (Large version)

We were getting really frustrated with clients asking us to define or optimize their mobile experience, when in fact they just wanted us to make things “prettier.” The slide above helps our client service directors to detect how potential clients really think about design. If we see that they don’t value our vision or approach, then we respectfully decline to work with them. Involvement starts with finding clients who want you to work with them, instead of for them.

Don’t Miss The Kick-Off

A kick-off meeting is the perfect opportunity to raise awareness of and appreciation for your mobile workflow. Learn as much as possible about the client, and find out how they would like you to help their business. Do this simply by asking about their vision, strategy and goals. Also great is to ask what inspires them and to get insight into their competitive research and analysis. From the minute you show true interest in their business, you are changing the way they look at you. By immediately working with them, you become their partner, instead of just someone who designs and codes.

A kick-off meeting is also a great time to double-check that you are on the same page. Sometimes we forget that our creative jargon might confuse clients. Big Spaceship points this out in its inspiring manual (PDF):

“We act like humans, we talk like humans, and we think like humans. And we call out anyone who does the opposite.”

In the last two years, I’ve learned that clients find it very hip to focus on responsive design, even if they don’t clearly understand it. Too often, it leads to a discussion on size and dimensions, when the conversation should be conceptual and strategic. Reserve some time in your kick-off meeting to explain what “responsive” means and why you believe in its value. Educate the client and steer the conversation towards what is really needed to make the project better. And if you notice that a certain topic needs more time and attention, host a mini-workshop to talk it through.

Dealing With Isolation

I don’t understand why some account and project managers try to keep their team away from the client as much as possible. Granted, it makes perfect sense that they manage the client, oversee the scope, deadlines and budget, and handle the communication and next steps. But when the work is in progress, keeping the team isolated doesn’t add any value. If this happens to you, explain to the manager that getting direct feedback from the client will help you fine-tune the product better and more quickly — a win-win for everyone.

At Little Miss Robot, we try to hold half of our meetings in our studio. Clients find it inspiring to be in this creative environment — especially because it is where their own product is being developed. In long-term projects, we also ask the client to designate a space at their office for our team to work on the project. When developing Radio+, we worked at the client’s headquarters twice a week. Anyone could hop in and out of the space and have informal conversations about the work. Not only did it create a great atmosphere, but we also received the most valuable feedback during these times. Highly recommended!

The Radio+ room, a shared workspace. (Large version)

Seeing Things

A typical project starts by the team exploring or defining what they will create. A lot of teams rely on textual aids, such as functional requirements. While these documents contain a lot of detail, I always end up having to address misinterpretations. The worst part is that these “minor” misunderstandings always pop up during the production stage, resulting in increased time and expenses. Have you noticed on these occasions that the client says they “saw” things a bit differently? This is why I recommend using text documents to scope features and using visual resources to describe them. Mind maps, wireframes, storyboards and paper prototypes are my personal favorites.

The wireframe for the Radio+ mobile website. (Large version)

I always encourage clients to get involved in generating these visual resources. Having them by your side during a brainstorm or a UX workshop is really helpful. While they wouldn’t consider themselves designers, I’m always challenged and inspired by their thinking and how they see things.

Feeling The Progress

Throughout the mobile development process, you will probably invite the client to several meetings to discuss the status of the project and to demo the product. Make sure you have something tangible to talk about. If a meeting is just about process, time or budget, then let the project manager handle it. Build momentum when meeting in person, and show your work in progress on real devices! Of course, you could print out the design or demo the application on a big screen, but the client should be able to feel the progress in their hands, too. Feeling a product grow in your hands is a much more powerful and engaging experience!

Some great tools exist to share designs across devices. We use AppTaster to share mockups, Dropbox to share designs and TestFlight to distribute apps to clients. If we are building a mobile website, then we just host it on the client’s servers internally, which allows them to view the latest version whenever they want.

Over-the-air beta testing for TestFlight. (Large version)

Happy Ending

Involving clients in your mobile workflow is the key to better understanding their problems, goals and strategies. You’ll also raise more awareness of and appreciation for your work, thus reducing negative energy and making discussions more positive and constructive. However big or small your team or client, it all starts with a desire to be involved. These take-aways can help you with that:

1. Create a manifesto that explains what your team stands for.
2. Hold a kick-off meeting to ask the client about their vision, strategy and goals.
3. Use both your and their offices to meet.
4. Scope features in text documents, and describe them in visual documents.
5. Take advantage of third-party tools to share your work in progress on real devices.

Last but not least, read Jeremy Girard’s article on how to wrap up a project and follow up afterwards. This is critical to building and maintaining a long-term relationship. Most importantly, it will lead to future business because the client will already know and value your work.

Please feel free to share your experiences and thoughts in the comments below. I’m already looking forward to reading them.

(al, ml)

© Thomas Joos for Smashing Magazine, 2014.