Feedback
Site Map
FAQ
Help
Tutorial
DAU
Home
News, announcements, training, search functions, Ask-a-Professor, and similar services with direct links supporting DoD acquisition.
Acquisition Process
Three processes cooperate to deliver capabilities needed by warfighters: the requirements process (JCIDS); the acquisition process (DAS); and the program and budget development process (PPBE). Includes links to DoD and Service policies, guidance, tools, and resources:
Workforce
Information on career management, the DoD Human Capital Initiative, career planning, leadership training, overarching planning and guidance documents, and relevant professional organizations.
Policy
Encyclopedic source of acquisition policy that follows a hierarchy of policy issuance (i.e., executive, legislative, federal, etc.) and filtered according to organization, career field, and special topics.
Communitiesof Practice
Links to communities of practice and special interest areas, the latest contribution and discussion posts for open ACC communities, community highlights, and links to related communities.
Training andContinuous Learning
Information on training and continuous learning that supports DoD acquisition, information that helps manage professional training portfolios, and information on training available from DAU and DoD and Services activities.
Industry
Information on DoD industry partners that helps the participation and execution of DoD processes; including industry support pages, news, information, and links to private sector acquisition contractors.
Displays tabs for additional AT&L Special Topics:
And popular AT&L Functional Gateways:
Portals
Functional Gateways
Fifteen functional knowledge gateways, one for each of the defense acquisition career fields.
Special Topics
Spcial Topics:
Better Buying Power Mission Areas MDID ACAT I/IA Support
Better Buying Power
News, policy, and media that support greater value and efficiency in defense acquisition.
S.L."Dusty" Schilling DSMC Executive Programs
Username:
Password:
Have recently returned from an extended vacation, which was very nice despite the stretch of 6 days with no power during the height of the heat wave.
Found in my inbox some guidance on preparing talking points for the USD(AT&L) and will share an extract at the end of this post.
Now the odds of me personally preparing any talking points for the Under Secretary are pretty much either slim or none; and if any reader of this blog is involved in such an effort they would be far better served getting the proper gouge then relying on something from me. Also, frankly, I am not much for bureaucratic formatting and process.
So why share this extract?
Because I believe the philosophy expressed here about effective communication is pretty good, and well worth reading.
As a PM you may consider using these simple concepts to focus your own (or your staff’s) thoughts regarding approaching meetings. An aspiring PM would do well to consider this guidance when you put together attempts to persuade management of something.
Partial extract follows:
TALKING/DISCUSSION POINTS FOR USD(AT&L)
Overall
· These points should be short but clear statements of major issues or points to be covered in the meeting. They should:
- Focus on achieving the objectives of the meeting.
- Be understandable as a stand-alone document, although more in-depth examination of the issues can be provided in the Read Ahead background document.
- Cover only the key elements of what the USD needs to know and be prepared to deliver or discuss.
Types of Meetings
· If an internal meeting, these discussion points should:
- Serve as guidelines for the discussion.
- Highlight any decisions the USD may be asked to make.
- Provide the highlights/key points the USD should take away from the discussion.
· If an external meeting, these talking points should:
- Provide the USD with crisp language to achieve the objectives/deliverables of the meeting.
- Be crafted to ensure a logical flow to the conversation.
- Highlight land mines to avoid or objections that may be raised.
Enter the code in the box below. (*required)