Inspired by Steve Ballmer's performance I decided to give an overview of different types of software engineers' characters. Various advices for self-improvement were also provided. Presented at local IT event - IT Weekend.
DISCLAIMER: All images were found either via Google Image Search, or on flickr.com
The document discusses the challenges of working with legacy code and whether it is better to rewrite the code from scratch or try to improve the existing code. It notes that programmers often want to rewrite code from scratch to build something new and exciting. However, the document advocates taking incremental steps to introduce tests and refactor small parts of the existing code at a time rather than attempting a complete rewrite. This helps minimize risks and ensures the essential parts are maintained as changes are made.
The document discusses the challenges of deciding whether to rewrite an existing codebase from scratch or work with the legacy code. It outlines reasons for not working with the existing code, such as missing documentation or tools. It also notes potential issues with rewriting from scratch, such as the impact on other teams and office politics. The document recommends starting by automating infrastructure and tests, learning the essential business concepts, and trying to introduce incremental changes to the legacy code before deciding to fully rewrite it.
This document discusses using technology in creating educational materials for teaching English. It outlines the objectives of learning how information and communication technologies (ICTs) can be used to design digital educational materials and distribute them online. Students will learn how to use some Web 2.0 tools and design virtual classes. They will also evaluate how effective the digital materials are. The document provides an example class agenda covering basic concepts like defining educational materials and ICTs, and how to search for information on these topics online. It assigns students a homework essay on why ICTs should be used for educational materials and how to prepare a PowerPoint presentation.
The document summarizes the qualifications and experience of Umid Abdullaev. He has experience in design, computer modeling and rendering, marketing, communications, and office administration. His skills include being attentive to details, solving computer problems, and being trilingual. He has worked as a research assistant, laser cutter operator, designer, design assistant, sales associate, and in university admissions. He has a Master's in Interior Design and Bachelor's in Industrial Design, and has received several awards and scholarships.
The document contains an agenda for a meetup group discussing various topics:
- An introduction and survey results will take place from 6:00-6:30pm
- A discussion on Behavior Driven Development (BDD) using SpecFlow will occur from 6:30-7:30pm
- Pizza will be served and mingling will follow from 7:30pm onwards
The presenter then discusses their perspective on BDD, how it allows for more readable automated tests through a syntax that can be understood by business stakeholders. A demo of BDD in action is shown using a tool called SpecFlow in Visual Studio. More information on the topic and a full code walkthrough is available on the presenter's
This document describes the design process for improving a biometric attendance system. It analyzes user interviews and heuristic principles to identify concerns with the existing system, such as the possibility of fake attendance and sensors not registering attendance. The proposed solution includes a push button with red and green lights and textured surface to grab attention. A blinking white light and optional camera would provide indications that attendance was recorded, while slight vibration and hidden features minimize confusion for users and administrators. The simplified, single button design aims to address identified usability issues.
Inspired by Steve Ballmer's performance I decided to give an overview of different types of software engineers' characters. Various advices for self-improvement were also provided. Presented at local IT event - IT Weekend.
DISCLAIMER: All images were found either via Google Image Search, or on flickr.com
The document discusses the challenges of working with legacy code and whether it is better to rewrite the code from scratch or try to improve the existing code. It notes that programmers often want to rewrite code from scratch to build something new and exciting. However, the document advocates taking incremental steps to introduce tests and refactor small parts of the existing code at a time rather than attempting a complete rewrite. This helps minimize risks and ensures the essential parts are maintained as changes are made.
The document discusses the challenges of deciding whether to rewrite an existing codebase from scratch or work with the legacy code. It outlines reasons for not working with the existing code, such as missing documentation or tools. It also notes potential issues with rewriting from scratch, such as the impact on other teams and office politics. The document recommends starting by automating infrastructure and tests, learning the essential business concepts, and trying to introduce incremental changes to the legacy code before deciding to fully rewrite it.
This document discusses using technology in creating educational materials for teaching English. It outlines the objectives of learning how information and communication technologies (ICTs) can be used to design digital educational materials and distribute them online. Students will learn how to use some Web 2.0 tools and design virtual classes. They will also evaluate how effective the digital materials are. The document provides an example class agenda covering basic concepts like defining educational materials and ICTs, and how to search for information on these topics online. It assigns students a homework essay on why ICTs should be used for educational materials and how to prepare a PowerPoint presentation.
The document summarizes the qualifications and experience of Umid Abdullaev. He has experience in design, computer modeling and rendering, marketing, communications, and office administration. His skills include being attentive to details, solving computer problems, and being trilingual. He has worked as a research assistant, laser cutter operator, designer, design assistant, sales associate, and in university admissions. He has a Master's in Interior Design and Bachelor's in Industrial Design, and has received several awards and scholarships.
The document contains an agenda for a meetup group discussing various topics:
- An introduction and survey results will take place from 6:00-6:30pm
- A discussion on Behavior Driven Development (BDD) using SpecFlow will occur from 6:30-7:30pm
- Pizza will be served and mingling will follow from 7:30pm onwards
The presenter then discusses their perspective on BDD, how it allows for more readable automated tests through a syntax that can be understood by business stakeholders. A demo of BDD in action is shown using a tool called SpecFlow in Visual Studio. More information on the topic and a full code walkthrough is available on the presenter's
This document describes the design process for improving a biometric attendance system. It analyzes user interviews and heuristic principles to identify concerns with the existing system, such as the possibility of fake attendance and sensors not registering attendance. The proposed solution includes a push button with red and green lights and textured surface to grab attention. A blinking white light and optional camera would provide indications that attendance was recorded, while slight vibration and hidden features minimize confusion for users and administrators. The simplified, single button design aims to address identified usability issues.
Prototyping allows designers to fail fast and improve designs iteratively. Designers may not effectively search the design space or recognize good designs. Prototypes are used to evaluate ideas, communicate with users, and provide feedback. Prototypes can be created at different levels from conceptual to screen design. Common techniques include rapid prototyping and incremental prototyping. Prototyping is best used when requirements are unclear, rejection costs are high, or user testing is needed before full implementation. However, prototypes may introduce early constraints and take significant time to create.
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
The document discusses why documentation is needed even for those who favor working software over documentation. It argues documentation is needed (1) for new team members to understand the system and (2) as a reference for current team members for parts of the system that are less clear. The document recommends documentation should include high-level pictures and maps of the system like diagrams of components and classes, as well as more detailed documentation for complex parts. It provides tips on how to select the core parts of the system to document and focus on documenting the "what" and "why" while letting code document the technical "what".
LeadMe is an app created by Evan Frederick, Samer Chahine, and Stephanie Wong that uses compass-like guidance to help users find friends in large unfamiliar areas or meet in quiet environments. The app detects nearby users and allows inviting or requesting help from friends through arrows that directly guide users to each other's locations. The creators plan to host LeadMe events, further polish the user interface, and publish the app in the Android Market.
This workshop/presentation by Shannah Segal covered of 7 important elements to responsive design. Specifically, what is responsive design, why is it important, and how do you need to approach this sometimes complex project.
Slides for a talk on "Making Sense of the Future" given by Brian Kelly, UKOLN at the ILI 2012 (#ILI2012) conference held at Olympia, London on 30-31 October 2012.
See http://www.ukoln.ac.uk/web-focus/events/conferences/ili-2012/a101/
Slides for a talk on "What Does The Evidence Tell Us About Institutional Repositories?" given by Brian Kelly, UKOLN and Jenny Delasalle, University of Warwick Library at the ILI 2012 (#ILI2012) conference held at Olympia, London on 30-31 October 2012.
Presentation by Åke Nygren at Internet Librarian International in London Oct 30 2012.
Session descriptions:
http://www.internet-librarian.com/2012/day.php?day=Tuesday#TrackC
http://lanyrd.com/2012/ili2012/szpfg/
Track C - Rethinking Connections
C101 - Social media strategies and policies
Moderator: Michael Stephens, San Jose State University & Tame the Web
How to step out of the library bubble using social media
Åke Nygren, Digital Services, Stockholm Public Libraries
Online connecting librarians
Wilma van den Brink, Library, Hogeschool van Amsterdam / University of Applied Sciences Amsterdam
Kitty Berteling, Hogeschool van Amsterdam
The social media landscape continues to evolve. Does your library have a social media strategy that can help you step outside the library bubble? By using such tools as Twitter, LinkedIn and Facebook, libraries can promote their services and products and bond with their patrons. This session will include practical examples of how librarians are using these platforms and the latest research on social media policies.
Este documento resume una presentación sobre marketing en redes sociales. Explica brevemente qué son las redes sociales, por qué son importantes para los negocios, y cómo pueden usarse para crear comunidades leales y hacer que los negocios crezcan. También identifica algunas herramientas clave de redes sociales y cómo funciona la comunicación viral.
A presentation & workshop I devised and gave/ran for the RSP - http://www.rsp.ac.uk/ - in 2009, looking at the future developments that might happen within UK institutional repositories. The event was held at the University of Bath.
A presentation to accompany a workshop I ran on behalf of UKOLN - http://www.ukoln.ac.uk/ - , University of Bath, at the Repositories Support Project Winter School in 2009 - http://www.rsp.ac.uk/. The workshop was designed to give repository managers an introduction to metadata as it related to their work.
RSP/SUETr Copyright & IPR Workshop, Northampton 2008Stephanie Taylor
A presentation to accompany a workshop I devised and ran for the RSP project - http://www.rsp.ac.uk/ - and the SUETr project - http://www.ukoln.ac.uk/repositories/digirep/index/SUE_Training_Programme:_SUETr - in the UK. The workshop was designed to teach repository managers in the UK the basics of electronic copyright & IPR as it applied to their own work.
A presentation I gave on behalf of UKOLN - http://www.ukoln.ac.uk/ - at the 'Doing Things Differently' event run by the RSP - http://www.rsp.ac.uk/ . The presentation looked at where institutional repositories might go in the future, the practical and the dream scenarios.
El documento presenta una introducción a las redes sociales. Explica que las redes sociales permiten a los usuarios crear perfiles públicos y compartir contenido como fotos, videos y actualizaciones de estado. También clasifica las redes sociales en diferentes categorías como redes sociales de microblogging, redes sociales basadas en intereses y redes sociales de fotos y videos.
The document discusses ways to expand the content and uses of institutional repositories beyond just hosting journal articles. It describes how the repository expanded to include electronic theses, grey literature, and research data. It also discusses providing metrics like downloads to authors and using the repository to support institutional goals like the Research Excellence Framework. Future plans include a project to unlock thesis data and using ORCIDs to better connect authors and outputs. The goal is to increase engagement by advocating for deposit mandates and showcasing the repository's value.
This document outlines a briefing on research data management (RDM) at LSBU. It defines RDM and research data, discusses why RDM has gained increased interest and attention due to factors like funder policies and legislative changes. It describes the benefits of RDM for researchers and institutions. It then outlines LSBU's RDM policy, which includes requirements for data management plans, data storage, sharing, and citation. The document discusses next steps for LSBU, including a survey of current practices, case studies, interviews, and launching an institutional data repository in 2016. It notes both opportunities, like training workshops, and challenges to implementing RDM, such as changing researcher behaviors and incentives.
A presentation to accompany a workshop I devised for the Repositories Support Project (RSP) in the UK, to teach repository managers about electronic copyright. 2008.
This document discusses best practices for managing product releases and software engineering teams. It provides the following recommendations:
1) Establish clear processes for releases, including regular intervals, versioning, distribution, and metrics to measure success. Ensure everyone understands their role in the release cycle.
2) Use the Dreyfus model of skill acquisition to balance team skills and experience levels. Recruit for "smart and get things done" attitudes. Apply practices according to where the team stands.
3) Automate aspects like releases, reporting, and testing when possible, but also retain some manual processes to aid understanding of what to automate. Team learning takes time.
Prototyping allows designers to fail fast and improve designs iteratively. Designers may not effectively search the design space or recognize good designs. Prototypes are used to evaluate ideas, communicate with users, and provide feedback. Prototypes can be created at different levels from conceptual to screen design. Common techniques include rapid prototyping and incremental prototyping. Prototyping is best used when requirements are unclear, rejection costs are high, or user testing is needed before full implementation. However, prototypes may introduce early constraints and take significant time to create.
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
Hi! We are Senti. We are looking for individuals who will bring new knowledge to our team. We are looking for pro-active and problem solvers to join our internship program!
The document discusses why documentation is needed even for those who favor working software over documentation. It argues documentation is needed (1) for new team members to understand the system and (2) as a reference for current team members for parts of the system that are less clear. The document recommends documentation should include high-level pictures and maps of the system like diagrams of components and classes, as well as more detailed documentation for complex parts. It provides tips on how to select the core parts of the system to document and focus on documenting the "what" and "why" while letting code document the technical "what".
LeadMe is an app created by Evan Frederick, Samer Chahine, and Stephanie Wong that uses compass-like guidance to help users find friends in large unfamiliar areas or meet in quiet environments. The app detects nearby users and allows inviting or requesting help from friends through arrows that directly guide users to each other's locations. The creators plan to host LeadMe events, further polish the user interface, and publish the app in the Android Market.
This workshop/presentation by Shannah Segal covered of 7 important elements to responsive design. Specifically, what is responsive design, why is it important, and how do you need to approach this sometimes complex project.
Slides for a talk on "Making Sense of the Future" given by Brian Kelly, UKOLN at the ILI 2012 (#ILI2012) conference held at Olympia, London on 30-31 October 2012.
See http://www.ukoln.ac.uk/web-focus/events/conferences/ili-2012/a101/
Slides for a talk on "What Does The Evidence Tell Us About Institutional Repositories?" given by Brian Kelly, UKOLN and Jenny Delasalle, University of Warwick Library at the ILI 2012 (#ILI2012) conference held at Olympia, London on 30-31 October 2012.
Presentation by Åke Nygren at Internet Librarian International in London Oct 30 2012.
Session descriptions:
http://www.internet-librarian.com/2012/day.php?day=Tuesday#TrackC
http://lanyrd.com/2012/ili2012/szpfg/
Track C - Rethinking Connections
C101 - Social media strategies and policies
Moderator: Michael Stephens, San Jose State University & Tame the Web
How to step out of the library bubble using social media
Åke Nygren, Digital Services, Stockholm Public Libraries
Online connecting librarians
Wilma van den Brink, Library, Hogeschool van Amsterdam / University of Applied Sciences Amsterdam
Kitty Berteling, Hogeschool van Amsterdam
The social media landscape continues to evolve. Does your library have a social media strategy that can help you step outside the library bubble? By using such tools as Twitter, LinkedIn and Facebook, libraries can promote their services and products and bond with their patrons. This session will include practical examples of how librarians are using these platforms and the latest research on social media policies.
Este documento resume una presentación sobre marketing en redes sociales. Explica brevemente qué son las redes sociales, por qué son importantes para los negocios, y cómo pueden usarse para crear comunidades leales y hacer que los negocios crezcan. También identifica algunas herramientas clave de redes sociales y cómo funciona la comunicación viral.
A presentation & workshop I devised and gave/ran for the RSP - http://www.rsp.ac.uk/ - in 2009, looking at the future developments that might happen within UK institutional repositories. The event was held at the University of Bath.
A presentation to accompany a workshop I ran on behalf of UKOLN - http://www.ukoln.ac.uk/ - , University of Bath, at the Repositories Support Project Winter School in 2009 - http://www.rsp.ac.uk/. The workshop was designed to give repository managers an introduction to metadata as it related to their work.
RSP/SUETr Copyright & IPR Workshop, Northampton 2008Stephanie Taylor
A presentation to accompany a workshop I devised and ran for the RSP project - http://www.rsp.ac.uk/ - and the SUETr project - http://www.ukoln.ac.uk/repositories/digirep/index/SUE_Training_Programme:_SUETr - in the UK. The workshop was designed to teach repository managers in the UK the basics of electronic copyright & IPR as it applied to their own work.
A presentation I gave on behalf of UKOLN - http://www.ukoln.ac.uk/ - at the 'Doing Things Differently' event run by the RSP - http://www.rsp.ac.uk/ . The presentation looked at where institutional repositories might go in the future, the practical and the dream scenarios.
El documento presenta una introducción a las redes sociales. Explica que las redes sociales permiten a los usuarios crear perfiles públicos y compartir contenido como fotos, videos y actualizaciones de estado. También clasifica las redes sociales en diferentes categorías como redes sociales de microblogging, redes sociales basadas en intereses y redes sociales de fotos y videos.
The document discusses ways to expand the content and uses of institutional repositories beyond just hosting journal articles. It describes how the repository expanded to include electronic theses, grey literature, and research data. It also discusses providing metrics like downloads to authors and using the repository to support institutional goals like the Research Excellence Framework. Future plans include a project to unlock thesis data and using ORCIDs to better connect authors and outputs. The goal is to increase engagement by advocating for deposit mandates and showcasing the repository's value.
This document outlines a briefing on research data management (RDM) at LSBU. It defines RDM and research data, discusses why RDM has gained increased interest and attention due to factors like funder policies and legislative changes. It describes the benefits of RDM for researchers and institutions. It then outlines LSBU's RDM policy, which includes requirements for data management plans, data storage, sharing, and citation. The document discusses next steps for LSBU, including a survey of current practices, case studies, interviews, and launching an institutional data repository in 2016. It notes both opportunities, like training workshops, and challenges to implementing RDM, such as changing researcher behaviors and incentives.
A presentation to accompany a workshop I devised for the Repositories Support Project (RSP) in the UK, to teach repository managers about electronic copyright. 2008.
This document discusses best practices for managing product releases and software engineering teams. It provides the following recommendations:
1) Establish clear processes for releases, including regular intervals, versioning, distribution, and metrics to measure success. Ensure everyone understands their role in the release cycle.
2) Use the Dreyfus model of skill acquisition to balance team skills and experience levels. Recruit for "smart and get things done" attitudes. Apply practices according to where the team stands.
3) Automate aspects like releases, reporting, and testing when possible, but also retain some manual processes to aid understanding of what to automate. Team learning takes time.
This document provides an overview of preparing for and succeeding in a technical interview process. It discusses finding job openings, the typical interview stages including phone screens and in-person interviews, common technical interview questions, and tips for each part of the process. The key advice is to practice coding problems daily, focus on breaking problems down step-by-step, ask clarifying questions, and follow up after interviews by thanking interviewers.
The document discusses the idea of a "360° developer" and the speaker's journey to becoming a well-rounded developer. Some key points:
- The speaker struggled when changing jobs from C# to Ruby, lacking context for agile practices and dealing with personality conflicts.
- They realized they needed to develop knowledge, personal, and functional skills to effectively solve business problems. This led to the idea of a "360° developer" with a diverse set of skills.
- The talk outlines developing skills in SOLID principles, design patterns, conflict resolution, mentoring, and cross-domain problem solving to become a well-rounded developer.
The document provides guidance for A Level media students on explaining the role of digital technologies and narrative in their coursework productions. It includes discussion of key concepts around digital technologies, narrative theories, and sample exam questions. For digital technologies, it highlights considering their use across pre-production, production, post-production, and evaluations. For narrative, it introduces several theorists like Propp, Todorov, and Neale and encourages applying their ideas to one of the student's productions. Homework involves outlining the digital technologies and narrative elements used in their projects.
Sharpest tool in the box: Choosing the right authoring tool for your learning...Brightwave Group
From rapid and responsive, to video and cross-browser capability we, as learning professionals, demand great things from the authoring tools available to us. And there are many to choose from.
This session explored the key factors we recommend you consider when choosing an authoring tool. These vary according to environment and culture, to the needs of your learners and the objectives of the learning. Choosing the right authoring tool and ensuring it is based on your needs ensures your learning content is not simply fit for purpose, but meets the aims of your wider learning strategy. With plenty of examples from real courses and solutions, the session covered a list of questions you need to ask, and provided a framework to help guide you through the tool-selection process.
● Great expectations - why the right authoring tool is the foundation of quality learning content.
● Key considerations - the right questions to evaluate the range of tools and make the right decision.
● The future - what can we expect from the next generation of authoring tools?
This presentation was delivered by Konathan Archibald and Nick Eastha, on Thursday 29th January at Learning Technologuies 2015 exhibition
Are you deploying technology and need to show executives what you have built? Then you must learn demonstration skills! Increase end user adoption and executive engagement by wowing your audience with your presentation skills. If you have IBM Cognos, Host Analytics, SAP, Oracle, or any software, it's time to let it shine in your presentations. I share my 25+ years of experience demonstrating software, so you look like a rock star.
The document provides information about a research and development course (Curso de I+D II) taught by Dr. Juan Manuel González Calleros at the Benemérita Universidad Autónoma de Puebla. The summary includes:
1. The document outlines the schedule, assignments, and important dates for the course. Students are expected to complete functional deliverables and validate user stories on set deadlines.
2. Assessment is based on partial exams, weekly advances, and a final delivery. Important dates include the first and second functional deliverables due on February 13th and March 22nd, and the final delivery due on April 28th.
3. Resources recommended for the course include textbooks on
The document discusses the process of creating digital work. It covers the key players involved, including agencies, clients, strategists, digital producers, production companies, coders, and UX/UI designers. It emphasizes collaboration between these groups. The document also outlines the project process, including phases like discovery, define, design, build, and testing. Key documents in the process are mentioned like functional requirements, technical requirements, site maps, wireframes, and design comps. Tips are provided for going live with the work and managing it after launch. Various online resources for inspiration and tools are also listed.
This document provides an introduction to basic project management concepts. It explains that the presentation aims to help readers without project management experience understand fundamentals. A project is defined as a set of interrelated tasks with specific objectives and resources. Examples include building construction, software development, and event planning. The document emphasizes that project management primarily involves soft skills like people management, communication, and documentation rather than technical expertise. It outlines initial steps such as identifying stakeholders, setting budgets and timelines, and using project management software and templates. Upcoming slides will cover documentation and a formal project workflow.
How to Effectively Lead a Focus Group by nexTier Product ManagerProduct School
Talking to users can be challenging or intimidating, and running a focus group is one of those tasks which most Product Managers would say is essential in getting real user insights. Traditionally, UX designers and Product Managers have relied on a combination of quantitative data and qualitative insights from focus groups and interviews.
Whether you want to test your user group's response to a new product or changes to modules or features within an existing product, as a product person you need to have a creative set of analytical skills and strategies for how to steer the group toward productive discussions.
Tremis Skeete talked about how focus groups can truly work well for you, and how you can organize, coordinate, and effectively lead focus group sessions.
Learn why you should do internships, how to choose, and of course, how to get them!
This was originally presented on 2nd September 2016 during Friday Hacks #116 hosted by NUS Hackers.
Watch a video of the presentation here: https://engineers.sg/video/friday-hacks-116-internships-and-why-you-should-do-them-nus-hackers--1105
This document provides information about technical interviews for computer-related jobs. It discusses the types of technical interviews, which include behavioral interviews to assess personality and fit for the company culture, and technical interviews to test skills and problem-solving abilities. Technical interviews typically involve multiple rounds with different interviewers and may include whiteboarding problems, live coding, and phone or in-person questions. The document provides tips for preparing for technical interviews such as practicing communication, staying calm, asking questions, and working through sample problems with an emphasis on process.
Game Design 2: UI in Games - Revision LectureDavid Farrell
The document provides an overview of the topics and content that will be covered in the Game Design 2 exam. It includes:
1) A reminder of the key topics and content from each lecture that could appear in the exam, such as menus, text, UI components, prototyping techniques, and usability principles.
2) Information about the format of the exam, including that it will contain 6 questions worth 10 marks each, and students must answer 4 out of the 6 questions.
3) Advice for students on how to focus their studying, including reviewing the content and examples from each lecture, as the exam will test understanding of both technical and conceptual aspects of the topics.
The document discusses Lean Startup principles for developing products, including building the minimum viable product (MVP) and getting customer feedback early in the development process. It provides an overview of concepts like customer development, product/market fit, and pivoting. The rest of the document demonstrates how to apply these principles through examples of developing personas, conducting product discovery research, and outlining the new product development process with Lean in mind.
How to Effectively Lead Focus Groups: Presented at Product School NYC Tremis Skeete
As seen on: https://www.meetup.com/productmanagementNY/events/247800115/
Talking to users can be challenging or intimidating, and running a focus group is one of those tasks which most Product Managers would say is essential in getting real user insights. Traditionally, UX designers and Product Managers have relied on a combination of quantitative data and qualitative insights from focus groups and interviews.
Whether you want to test your user group's response to a new product or changes to modules or features within an existing product, as a product person you need to have a creative set of analytical skills and strategies for how to steer the group toward productive discussions. Let's get together to discuss how focus groups can truly work well for you, and how you can organize, coordinate, and effectively lead focus group sessions.
Main takeaways:
- The do's and don'ts when leading focus groups
- What it takes to guide a productive conversation and avoid groupthink
- How to connect with participants in order to generate informative responses
- Ways to articulate your focus group strategies
- Methods for asking questions and capturing insights
Meet the Speaker: Tremis Skeete
Tremis is a Technical Product Manager at NexTier Innovations, a management consultancy specializing in Multi-Dimensional Analytics, Project Portfolio Intelligence, and Enterprise Cyber and Infrastructure Security. He comes from a Computer Science background and has 15+ years of experience working with design teams. He has helped clients such as Zel Technologies, The Altria Group, Barclays Bank, US Department of Defense and L’oreal. During his time working with these companies he helped build web sites, applications, intranets, and graphic communications across multiple platforms.
The document provides an overview of the role of a Chief Technology Officer (CTO). It describes the CTO as the CIO's right-hand technical strategist who defines technological strategy, assesses technical risk, establishes standards, and evaluates both teams and new technologies. The CTO also identifies areas needing improvement, helps with post-production, and advises other disciplines. The CTO typically has a background in applications development or systems architecture and enjoys technology and solving complex problems.
User-centered design (UCD) is a design philosophy that focuses on the needs of users throughout the design process. The document discusses the key steps in UCD, which include defining the project and users, creating concepts, designing visual solutions, development, and deployment. It emphasizes early and continuous user research methods like interviews and usability testing to help ensure designs meet user needs.
Sharpest tool in the box: Choosoing the best authoring tool for your learning...Brightwave Group
From rapid and responsive, to video and cross-browser capability we demand great things from the authoring tools available to us. And there are many to choose from.
This presentation explores the key factors we recommend you consider when choosing an authoring tool. These vary according to environment and culture, to the needs of your learners and the objectives of the learning. Choosing the right authoring tool and ensuring it is based on your needs ensures your learning content is not simply fit for purpose, but meets the aims of your wider learning strategy.
In this three hour workshop I present an introduction to the UCD process, an overview of the basic technologies of the web and a survey of current Mobile Web Design trends.
4. What you DON’T need -
• A technical background
• An ability to write code
• A knowledge of every possible technology that
could be used
5. What you DO need -
• An ability to clearly describe what you want
something to DO
6. Start with a workflow
• Think through & describe the steps of how
something should work
7. Then draw up your requirements
• Make a list of what you need the technology
to do
• Note any specific standards the technology
will need
• Note any systems or other technologies the
new technology needs to interact with
• Any other important things it needs to do
8. Let everyone do what they do best
• You know best what you want to be able to do
with a tool
• Let the developer(s) sort out exactly how this
is done – that is not your problem
9. Talk The Same Language
• Be very clear about what you both mean.
10. Be Flexible
• You don’t have to understand all the technical
details, you just need to be able to understand
how something might impact on your
workflows to make a decision.
• Keep talking- it’s about teamwork.
11. The Hardest Things Of All
• It’s your call in the eternal time versus
perfection battle
• Let the developers get on with it – trust their
expertise
12. And don’t forget…
• Development teams need regular supplies of
kittens, coffee, cake & beer
Thankyou!