Related Content
![]() |
Getting Coworkers to Like You Even software professionals need to know how to be well-regarded in the workplace. Naomi Karten presents some tips on how to get coworkers to like you. |
|
![]() |
Tips for Starting (and Ending) a Process Analysis Without boundaries, a process analysis could go on forever. Adapting things learned from working in agile software development, Scott Sehlhorst provides tips for starting—and ending—a process analysis. |
|
![]() |
How to Stay Awake during a Boring Meeting Have you ever had a hard time trying to stay awake during a boring meeting? Here are some tips to keep you alert, attentive, and wired during a potential snoozefest. |
|
![]() |
How to Hold On to Your Job during a Merger Although there is no sure way to survive a merger, there are many things you can do to hold on to your job. From knowing how to deal with office politics to being a team player, there are several ways you can significantly improve the odds that your job is secure. |
|
![]() |
Apologizing: Good Idea or Means to Manipulate? An apology can defuse anger, restore goodwill, and mend damaged relationships. And, often, an apology is just the right thing to do. Research shows that apologies in innocuous situations can counteract annoyed responses, and some hospitals have even established medical apology programs. |
|
![]() |
The Case for Napping on the Job Napping is healthy. Just ask a cat! And, there’s growing evidence that humans napping during work hours can boost their energy level, or at least prevent its decline. Napping also can improve cognitive functioning by speeding up and improving memory consolidation. |
|
![]() |
There's No Such Thing as a Freemium Lunch The freemium business model—in which some users use the product for free, and others use it for a fee—can be appealing. To succeed with the freemium model, you must first acknowledge that a revenue plan is not a business plan and then decide if it makes sense for your bottom line. |
|
![]() |
Bug or New Requirement – Does It Matter? The terms "bugs" and "requirements" indicate who is responsible for the problem. No matter which term is used for the current state, the current state needs to change. Only then can the focus shift to fixing the problem. |