Need to quickly identify a typeface? Here's a handy gadget that should help. Take a screenshot of the type and upload it on:
http://www.myfonts.com/WhatTheFont/
Bam! You're welcome. Mama G
Dallas
1997
Life does not cease to be funny when people die any more than it ceases to be serious when people laugh. (George Bernard Shaw)
I do not want my house to be walled in on all sides and my windows to be stifled. I want all the cultures of all lands to be blown about my house as freely as possible. But I refuse to be blown off my feet by any. (Ghandi)
• Revolutionary • Mentor • Philosopher • Writer • Mama G
Need to quickly identify a typeface? Here's a handy gadget that should help. Take a screenshot of the type and upload it on:
http://www.myfonts.com/WhatTheFont/
Bam! You're welcome. Mama G
|
IMAGINE: How Creativity Works Coolness... About this video: |
The tribal wisdom of the Dakota Indians, passed on from generation to generation, says that "When you discover that you are riding a dead horse, the best strategy is to dismount." However, in many organizations a range of far more advanced strategies are often employed, such as:
Dear Team: We have a problem. If you dread communicating project glitches, take heart—telling folks your project is facing issues is rarely a fun task, but here are some suggestions on how (and why) to get bad news out in the open.
1 – Say it early. Unless it’s an issue you’re certain can be handled internally without any detectable effects on stakeholders, you’re best off sounding the alert early. End users and supporters are more likely to be amenable to solutions that impact timeframes or final objectives if they can see you’ve been proactive and upfront with them.
2 – Say it clearly. Now is not the time for buzzwords or vague project-speak—confusing your stakeholders will only make them more unhappy. Instead, plainly state the issue, along with its triggers (if you can). Misunderstandings certainly won’t build support for whatever solution you implement, so lay out the facts in understandable language.
3 – Say it without blame. The urge to point fingers may be strong, but now is not the time to indulge it. Even if a team member or a vendor completely dropped the ball, it’s better to deal with the issue professionally—and with the vendor directly—than to air your grievances far and wide.
4 – Say it with a solution. You may not have completely formulated a plan to deal with the problem yet, but framing the issue along with a possible resolution will often go a long way toward maintaining stakeholders’ confidence in your abilities. Be sure to delineate where the plan is still in development, so you aren’t inadvertently setting expectations you may need to revisit later.
(Excerpted from PM Alliance’s Project Management Blog)
In the beginning was THE PLAN.
And then came The Assumptions.
And The Plan was without substance.
And The Assumptions were without form.
And darkness was upon the face of the Workers.
And they spoke among themselves, saying,
"It is a crock of s--t, it stinks."
And the workers went unto their Supervisors, and said,
"It is a pail of dung, and none may abide the odor thereof."
And the Supervisors went unto their Managers, saying
"It is a container of excrement, and it is very strong,
such that none may abide it."
And the Managers went unto their Directors, saying,
"It is a vessel of fertilizer, and none may abide its strength."
And the Directors spoke among themselves saying one to another,
"It contains that which aids plant growth, and it is very strong."
And the Directors went to the Vice Presidents, saying unto them,
"It promotes growth, and it is very powerful."
And the Vice Presidents went to the President, saying unto him,
"This new plan will actively promote the growth and vigor of the company, with powerful effects."
And the President looked upon The Plan, and saw that it was good.
And The Plan became policy.
And that is how S--t happens.
0 comments