When planning a new program, I first try to learn what has already happened and been successful elsewhere or in the past. Rather than reinventing the wheel, I want to take a past iteration and build off of it to create something that is effective for my local, current audience. I also really like making lists, and actually writing out/brainstorming different ideas, thinking about things from various angles and steps of the process, then I'll share my idea with others to get their input and modify/adapt my plan.

Planning a new program can be very difficult. I think one of the most important part of it is finding something you are passionate about. If we do not have the passion for doing something, we might not do as good of a job as we would if it was something we were motivated about. I personally am someone who writes everything down and likes to see it on paper. I am a firm believer in making sure that work is not overlapping with others. Collaboration is so very important when it comes to things so you know you are headed in the right direction. I find picking other peoples brains the most important. Go to the experts who have done it and build off of what they did and improve upon it.

Developing my current Travel Training program has involved reaching out to other organizations in the community to see what (if anything) they already do related to the topic.
We of course want to encourage and support whatever currently exists, and don't want to create extra steps if we can borrow from others, or make their programming more robust with our involvement.
Admittedly, I'm prone to going digital first - but was pleasantly surprised by how responsive people are by phone!
In the case of a specific addiction recovery service in our community, I just had to show up in person and see who I could speak with. This went incredibly well, as that particular organization wasn't used to people coming in and offering support and solidarity.
Sometimes it's a generational/culture gap in terms of communication, or maybe it's just a matter of staff capacity and availability.

Much like many of you are describing! I like to research, draw, think with others....and document what I'm hearing. Where I work our process is typically to develop a proposal for leadership - who like to see what I've found/heard/planned (and the price tag that might go with things). Not everything is that formal...but when I do have things written down it tends to take it to the next level - particularly if there is space and time to identify funding.

When I start planning a new program, I generally talk to my colleagues to determine what would be the most useful event to host for the community. I always learn a lot from these discussions, so I really value the time I spend collaborating with my coworkers. From there, I start to create an itinerary, and list out everything that needs to happen before the event, whether that is creating flyers, social media posts, or finding money in the budget for all the necessary expenses. After I brainstorm on my own, I usually ask others for the opinions so that I can get a different perspective on my event.

When program planning, I like to familiarize myself with the programs that we already have offered. From there, I discuss with colleagues on their thoughts of these programs, and what our current community needs and priorities are. I then research similar programs and see what can be adopted and modified for our own local needs. Once I have a written draft, I like to pitch my ideas or openly discuss them again with colleagues. I like open discussions because of all the unique perspectives it brings up that may shape and change the program or help me solidify my goals and objectives.

When planning a new program, I first talk to with my colleagues around the office. I want to learn what worked from them and what didn't, so I can try to avoid potential pit falls. I like to then write out my ideas. After having a more concise idea of what I want to do I research similar programs that were conducted through other extension offices. I will also share my ideas with my colleagues as they come together.

When planning a new program the first thing I do is Google. I love Google and often wonder how people looked up things before it. (I know it was in books, but that seems like such a long process compared to just typing in a word) My main objective at this beginning stage is just collecting ideas: looking to see how things were done by others and then tying together all the different aspects I like to create something new. I am very inquisitive, and this can often lead me down a rabbit hole of information, but sometimes I find things there that I never even considered. I am a pen and paper note taker, but don't find myself using these tools when I'm Googling, I think they could help. Once I have an idea of what I want to do I talk with others in the office about it, and try to use their experience and expertise to help me fine-tune my thoughts and implement them.

When planning a new program, my first step is to talk to colleagues about what has been done in the past. I think it's good to find out what worked and what didn't work if there has been a similar program and also to get ideas from colleagues first. Then I like to google to find similar programs and to get ideas from them. And then probably the next step for me would be to bounce new ideas off of colleagues once again.

I have identified a need, then think through approaches that could be taken to address it. Then I meet with staff and appropriate colleagues that can contribute to a program for ideas, resources, etc.. This can be in the form of phone calls, emails and meetings.

I think programming usually starts with discussions about a need/issue  you discover. Discussions with colleagues will broaden and refine your ideas regarding the need. Brain storming on approach/how to reach the audience, how to implement, market and fund the program will follow but I think understanding the need fully must be the initial step.

When planning a new program depending on the topic I would see what has been done already in the past so there isn't redundant repetition. Once that has been identified I would share the idea with colleagues pertinent to the program examining different viewpoints to start making decisions on how to best implement.

For me the process of program development seems very logical and process oriented. Right up my alley. For me the challenge will always be that of Time Management. It always seems to me that there is less and less "free time" and more and more "items" aka projects getting added onto the plate. Suggestions?

Many times we have programs that are brought to us by our constituents, so we may have the beginning of a program, but need to develop it further especially to meet the priorities of a request for proposals. Specifically, we work with the commercial fishing industry. They often come to us with an issue that we can collaboratively help them solve. The issue here is locating the right funding mechanism to address the issue.

When planning a new program, after identifying a need, I feel it is most helpful to me to write out a plan and let it sit for a day or two (I get too attached to get feedback immediately). Then, I discuss with colleagues. With feedback, I change the plan and adapt as needed. Finding a need in the community that I am also passionate about and is exciting definitely helps keep me engaged in the topic and that excitement boils over into the implementation and program participants as well.

I approach a new program to determine a need for the program or a business opportunity, since not everyone knows what they need/want.

For beginning a program, i reach out to my colleagues for the concept phase of a program

I follow the project management system Scrum to break down the program needs into backlog items, from there i am able to assign items for a series of 2-3 week intervals (Sprints). i can then organize multiple sprints to get a timetable of the program and visualize who is working on what plus their progress.

Planning a new program for me would look at the reasons why we are doing the program- what is the needs addressed, the people we are looking to work with and for, if the program has already been implemented in other places and if there is some level of collaboration, or outreach that can be done so there isnt reinventing the wheel.
The first strategy I find helpful is to understand why---how did this idea come up, why are we working on the specific part of a problem, etc.
Another strategy is to look at it from a different perspective, - understand if there is a reason why it wouldn't be beneficial; will it actually hurt people rather than help them; what are unintended consequences that may be associated with addressing the problem.
For instance- if a country wanted to make 80% of their population drive electric cars by a certain date; the problem being addressed is car emissions- reduce pollution due to car exhaust. However, what may not be considered is the heavy metal waste and unhealthy working conditions for creating the batteries for the car, the need for increased electricity and electric infrastructure; the waste associated with the increased electricity and production of car batteries. And the cost of electric versus the cost of gas for the regular consumer. How do people charge their cars when living in large apartment complexes, etc.

To plan a new program, there must first be a need, problem, concern, or question that needs to be address. Basically, there needs to be purpose. Once there is a purpose for your program, you then need to figure out what stakeholders/funding sources share a similar interest in what you want to pursue for your program. You then need to approach the stakeholders/funding sources, whether it be directly via email or phone (small funding sources typically) or through pre-proposals/proposals (typically large agencies, such as USDA, FDA, NOAA, etc.). Once you have found stakeholders with similar views who wish to fund your program, you then need to create a plan of implementation/experimental design and finding the right individuals to have as part of the program team. Once you have an overall goal, funding, program plan, and staff, move forward with your first program project(s). Review project outcomes, downfalls, knowledge gaps, staff performance and expertise. Once review is complete, find problems/questions associated with the experience you and your team have gained, and apply it to the next round of finding funding, expanding staff, etc.

To approach planning a new program, I would first identify the need for the program and the funding availability. The audience is very important for program development because you need to tailor the program to an audience. Decide on program objectives and create a logical flow to the program for successful implementation. Next you implement the program to the audience in a way that is accessible and fun for the community. Making it a memorable experience can include using hands-on exercises and activities that engage the senses. After the program is implemented you should access whether the objectives were met and gauge how successful the program was so that you can make adjustments or improvements. Using evaluations can help provide the data to make the program better. Program development is an iterative process and requires continual reflection, adjustment, and practice.

I try to start with a big picture and the desired outcome. Sometimes I am replicating something already done so I would start with the creators--what worked, what didn't. Information gathering. Our staff is a tremendous resource with varied backgrounds so brainstorming helps identify any missing components and keeps me open to trying old things. I have been around long enough that there is very little that is brand new. Maintaining and supporting that spark while utilizing the knowledge we have gained goes a long way.

Approach would be closely linked to needs as well as staff expertise. Ensuring that as extension staff, we are listening and engaging with stakeholders in various ways so that we can hone our understanding of the local community need is the first step. Next would be developing how these needs align with our expertise and develop programming through collaboration.

Once a need has been identified, the process of program planning begins. Then you conduct an assessment of multiple aspects that make up a program, ie. the level of funding, staff availability, community and engagement, and competition. You should engage with department leads, funders, stakeholders and the community serviced. Starting small with a Pilot may be the best course of action to start the program, see how it works, establish reporting and evaluation structures and then assess next steps.

When developing a new program, I look and listen to what is happening around me. A new trend, a new idea, something that first interests me and then see what audience also is interested in this topic. Write down ideas, brainstorming on my own first. Then get feedback from colleagues. Colleagues adding their thoughts and ideas and experiences are always helpful.

When planning a new program I assess the situation, reviewing risks and needs of the company, employees and customers. I then discuss those with managers to obtain their assessments and feedback on the situation. Then I determine if this is an immediate need or is it a short, or long term goal.