Be honest with your management team, make sure they know. Don't ever try to mislead people about the scope of your knowledge - it doesn't impress them and only causes you problems.
Work with your team to evaluate your options - it may be possible to change technologies, or perhaps someone else in the organization can help mentor or support you. Changing course earlier on is easier and less expensive than later.
Adjust your project timeline to take into account the potential risk and delays caused by working beyond your core strengths. If you don't have enough knowledge to estimate the risk, be very conservative in the confidence factor of your estimates and timeline.
Look for an expert in the domain/technology and see if you can engage them either as a consultant or advisor on your project. Nothing makes a bigger difference than prior experience in a domain.
Take some time to try to create a simpe prototype or proof-of-concept in the domain/technology you will be working on. Look for possible issues that could emerge. Sometimes unexpected problems surface when you try to create a simple prototype - this can help steer the effort when working on the real thing.
See if the scope of your project can be scaled back. If you are already "behind the curve" the best way to improve your odds of success is tackling something smaller, rather than larger.
Seek out advise from people you trust. Especially people whose expertise and knowledge has some bearing on the problem or technology you're taking on. They may be able to give your more specific advise or ideas.
You have to take it outside the company to someone (person or consultancy) that can complete it. This means a contractor/consultant that will be with you for a temporary period of time. If possible have them work in house with your and your team and make part of their responsibility to train you.
You may have to explain to management that without this, the project could fail and will probably be late and over budget. Don't worry about outsourcing some projects - you and your team will still have lots of work.
Temporarily hire someone who has the expertise you're missing, and make sure they're prpared to transfer their knowledge to others in your team as well as work on the problem at hand. Be prepared to pay serious money; but if the problem really is complex, chances are you'd take much longer, get a much worse result, and pay more overall if you try to figure out out without any help.
您的前进道路应该考虑这是否是您的公司内部需要拥有的技能/技术，即“能力”。根据这一点，听取@Oded（外包）或@Michael Borgwardt（雇用承包商进行一些知识转移）的建议，或者花费大量时间（如果有的话）并自行开发该功能。例如，假设您要与某些购买的软件包进行交互，该软件包以某种二进制格式输出幻数。聘请承包商来编写界面。假设您的履行副总裁希望您与 FedEx Web 服务进行交互，而您公司中没有人了解 SOAP。您知道，将为所有供应商和合作伙伴提供更多 SOAP。您需要内部 SOAP 技能，因此接受一些培训、制作原型，也许还需要一些外部帮助。
First, +1 to Borgwardt, Oded, Bushkin. Great answers here. Now my two cents...
Your path forward should consider whether this is a skill/technology i.e. "capability" that your company needs to have internally. Depending on this, take the advice of either @Oded (Outsource) or @Michael Borgwardt (hire a contractor to do some knowledge transfer), or spend a lot of time (if you have it) and develop the capability on your own. For example, suppose you're going to interface with some purchased package that spits out magic numbers in some binary format. Hire a contractor to write the interface. Suppose your VP of fulfillment wants you to interface with a FedEx web service, and nobody at your company knows SOAP. And you know that more SOAP is coming, for all suppliers and partners. You'll need SOAP skills in-house, so get some training, do a prototype, and maybe bring in some outside help.
发布评论
评论（4）
您必须将其带到公司外部，交给可以完成它的人（个人或顾问）。这意味着承包商/顾问将暂时与您在一起。如果可能的话，让他们与您和您的团队一起在内部工作，并承担培训您的责任。
您可能必须向管理层解释，如果没有这一点，项目可能会失败，并且可能会延迟并超出预算。不要担心外包一些项目——您和您的团队仍然有很多工作要做。
You have to take it outside the company to someone (person or consultancy) that can complete it. This means a contractor/consultant that will be with you for a temporary period of time. If possible have them work in house with your and your team and make part of their responsibility to train you.
You may have to explain to management that without this, the project could fail and will probably be late and over budget. Don't worry about outsourcing some projects - you and your team will still have lots of work.
暂时雇用拥有您所缺少的专业知识的人，并确保他们准备好将自己的知识传授给您团队中的其他人并解决手头的问题。准备好付出大笔金钱；但如果问题确实很复杂，如果你试图在没有任何帮助的情况下解决问题，你很可能会花费更长的时间，得到更糟糕的结果，并且总体上付出更多的代价。
Temporarily hire someone who has the expertise you're missing, and make sure they're prpared to transfer their knowledge to others in your team as well as work on the problem at hand. Be prepared to pay serious money; but if the problem really is complex, chances are you'd take much longer, get a much worse result, and pay more overall if you try to figure out out without any help.
首先，+1 给 Borgwardt、Oded、Bushkin。这里有很好的答案。现在我的两分钱...
您的前进道路应该考虑这是否是您的公司内部需要拥有的技能/技术，即“能力”。根据这一点，听取@Oded（外包）或@Michael Borgwardt（雇用承包商进行一些知识转移）的建议，或者花费大量时间（如果有的话）并自行开发该功能。例如，假设您要与某些购买的软件包进行交互，该软件包以某种二进制格式输出幻数。聘请承包商来编写界面。假设您的履行副总裁希望您与 FedEx Web 服务进行交互，而您公司中没有人了解 SOAP。您知道，将为所有供应商和合作伙伴提供更多 SOAP。您需要内部 SOAP 技能，因此接受一些培训、制作原型，也许还需要一些外部帮助。
First, +1 to Borgwardt, Oded, Bushkin. Great answers here. Now my two cents...
Your path forward should consider whether this is a skill/technology i.e. "capability" that your company needs to have internally. Depending on this, take the advice of either @Oded (Outsource) or @Michael Borgwardt (hire a contractor to do some knowledge transfer), or spend a lot of time (if you have it) and develop the capability on your own. For example, suppose you're going to interface with some purchased package that spits out magic numbers in some binary format. Hire a contractor to write the interface. Suppose your VP of fulfillment wants you to interface with a FedEx web service, and nobody at your company knows SOAP. And you know that more SOAP is coming, for all suppliers and partners. You'll need SOAP skills in-house, so get some training, do a prototype, and maybe bring in some outside help.