Turn on more accessible mode
Skip to main content
Turn off more accessible mode
Sign In
This Site
This List
Home
Blogs
Ask a Question
News
Chat
Events
Wiki
Resources
Webinars
WorkSites
Surveys
Podcasts
Jobs
Topics
Suggestions
Tips
Help
>
Localization Tip
Localization Tip
Quick Launch
Lists
Popular Tweets
Sites
Add a file
Member files
Newsletters
Pictures
Member Photos
Report Inappropriate Content
Modify settings and columns
Actions
View:
All Items
Tip
Count = 36
A good leader...owns their subordinate's problems and pursues them with the same vigor they would for their own problems.
A good leader...does not horde useful information in order to obtain leverage.
A good leader...does not micro-manage.
A good leader...rewards openly and punishes privately.
A good leader...trusts and stands up for their people. Get to know them. Don't let outsiders attack them. Don't be a spy for your superiors.
A good leader...leads by example. Don't do anything you wouldn't want subordinates to do.
Negative emotions illicit narrow, immediately actionable thinking aimed at survival in the present moment while positive emotions generate a more expansive range of behaviors; i.e., more creative, accurate, and generative, tolerant and inclusive thinking.
67% of the competencies necessary to be a successful manager/PM are emotional competencies: personal competencies of self-awareness, self-regulation, and motivation and social competencies of empathy and social skills.
Improve a mechanical device and you may double productivity. But improve people...and you gain a thousand fold. Khan Noonien Singh, Star Trek, Season 1, Episode 22
Every place where data travels from one tool to another is a place for problems to occur.
If you look for tools that provide the best quality for each piece of a system you can end up with a puzzle where pieces don't fit. Like a sports team, a system of parts that work well together often beats a system of 'star' parts that don't.
Big bang system implementation vs iterations. Big bang puts people through a big change only once and funding may not last to realize iterations. However, iterations allow you to stabilize each step so you build on a solid foundation towards an end state.
It is important to keep reminding management of the value your efforts generate.
People base their assessment of new systems partially on their experience with previous ones. If you had an inefficient process before it is easier to show value with a new system. If you had a good system before it will be more difficult to exceed it.
People get attached to the way they do things and usually want new systems to behave like the old one. Often, no new approach works for everyone but the way they've been doing things is merely the best way they could think of so far and can be improved.
In a new system you will have new problems; problems people are not comfortable dealing with.
People see what's worse more clearly than what's better. New things people have to do or can no longer do in the new system are immediately obvious. Less obvious are the advantages of the system.
Any system that requires people to give up control for the greater good of the organization will meet resistance.
More automation means more integration with complex systems.
As expensive as they are, enterprise tools often don't do basic things you need.
This tip left intentionally empty. If you don't like this tip or any others, simply click Refresh on your browser. :)
It is pertinent for virtual team members to meet face-to-face at least once; preferably at the beginning of a project.
Highly disclaimed numbers beat the best qualitative statements any day.
Terminology is foundational to all other localization processes.
There are many ways to get the work done. Your way is not the only way. It may not even be the best way.
No one likes to be around negative people; even if they agree with the reason for the negativity.
Don't take criticism personally. It's about the work; not you. Besides, you can't fix what you don't recognize as broken. A realization of weakness is requisite to becoming strong.
Definition of an overloaded Resource - Someone who does lots of things poorly at the same time.
AASM - Avoid it if possible, Automate what you can't avoid, Semi-automate what can't be automated, and as a last resort...do it Manually.
A given process assumes a level of scope, importance and other things about the task. Processes need to be flexible enough to adapt to tasks with different characteristics.
A 'schedule' can be anything from a huge MS Project file to a few spoken words; i.e., "We'll be done next Friday" or anything in between.
Not everything has to be perfect.
Use the minimum number of translators possible to meet the schedule. This will minimize communication needs while maximizing consistency.
The paying client has the final say.
Quality is subjective.
HT is better than MT which in turn is better than NT.
Powered by
Worldify
| Windows SharePoint Services® |
L10NCafe Membership Agreement