27 jun

Soft Skills: Feedback

Soft Skills

About a month ago Portiva started a two year Program called “Portiva Samen Groeien” (Portiva growing together”). Therefore we started a partnership with Pam and Bernard from Carv Company. They are going to teach us Soft Skills related to the topics “Me”, “The Team” and “The Customer”.

It all started with us filling in a personality test of about 150 questions. During a 1-on-1 with Pam, we would talk about our results and think about our personal goals for these two years.

Next to these 1-on1 sessions we also have group sessions. The first group sessions was about the topic “Feedback” and here I would like to post what I learned about “Feedback”.

Let’s start with some definitions.
A compliment is an expression of praise. Just like saying “I like your hair”.
Criticism is the practice of judging something or the behaviour of someone according to standards/criteria. e.g. “The dutch soccer team did not play very well this year during European Championship”
Feedback ‘is a process in which information about the past or the present influences the same phenomenon in the present or future.’ (Wikipedia). Which means you give feedback about something in order to influence the future. For our context it is important that feedback should always be about behaviour. Feedback can be positive, if you want the same behaviour to happen again; or negative, if you want to change the behaviour.

During the sessions we learned some steps, in order to give feedback in a proper way:
If you follow these steps, you have a good chance of being heard, accepted and achieve your goal:

  1. Describe the behaviour you have seen in the other person. Describe it from an “I have seen” perspective.
  2. Ask the other person if she has also noticed this behaviour in herself, if she can recognize herself in your words. In the case that you do not find agreement at this step, then there is no point to continue.
  3. Describe how this behaviour affects you… which feelings you get from the other persons behaviour.
  4. Together, try to interpretate the situation and why you got there.
  5. Together, try to find a solution.

We got the assignment to give and ask for feedback from different people using these guidelines.

During this assignment I actually learned the most, about why the rules are important.
(1) Because you are describing in the “I have seen” perspective, the other person cannot argue with you. You have seen what you have seen.
(2) If you then ask the other person tell you if she recognices this behaviour in herself, this is the point where the other person hardly can say no. Even if she was not aware of this behaviour so far, but she will think about what you have seen, she will likely become aware of her behaviour. (of course with the assumption that the behaviour is really taking place)
(3) If you the explain which feelings you get from this behaviour (irritation, anger, happiness) you will make it personal on your side. This will be the moment why the other person will understand why you want to give the feedback and why it is so important for you to get this out.
(4-5) Trying to interpretate and finding reasons for the behaviour at this late stage in the conversation, makes the most sense. You both already agreed the the behaviour is taking place, and you have already made it personal and important. So both of you are neutral and will be open for the interpretation and solution.

So as a little summary:
give feedback on the behaviour of someone else, if it triggers strong feelings in you, and you want to influence the behaviour in the future.
follow the rules of giving feedback for it to be the most successful

One of the most important things I’ve learned, is to be open when you go into a feedback conversation. Do not try to figure out why the other person is behaving in a certain way, before the conversation. You will have time and space in your conversation for doing so together.

Read More

18 jun

Portiva zoekt kandidaten! Interessante rol als SharePoint Business Consultant bij dè 100% SharePoint club van NL

Portiva No Response


Click hier voor meer informatie:

Als SharePoint Business Consultant opereer je tussen Business en IT. Je adviseert klanten over de inzet van Microsoft SharePoint voor thema’s als ECM, collaboration, BPM, portals of search. Business cases werk je verder uit in functionele ontwerpen en advies rapportages.

Binnen het projectteam vertaal je het ontwerp naar een concrete SharePoint oplossing waarbij je gebruik maakt van diepgaande technische kennis van collega’s waar nodig. Je opereert nadrukkelijk aan de klantkant en bewaakt de functionele wensen en eisen van de klant gedurende de realisatie. Je overtuigd op kennis en ervaring m.b.t. SharePoint maar ook op bedrijfskundig niveau. Je zit aan de voorkant van projecten en afhankelijk van je achtergrond en ambitie vervul je de rol van lead SharePoint consultant of Projectleider.

Je bent ondernemend en naast billable werkzaamheden ondersteun je het management op het gebied van de ontwikkeling en positionering van Portiva. Bijvoorbeeld door het verder ontwikkelen van de Portiva eigen project en consultancy methodologie; genaamd Portiplan.

Click hier voor meer informatie:

Read More

08 mei

Portiva #SharePoint Seminar Serie Mei 2012 #MicrosoftNL

Portiva, SharePoint 2010 No Response

Schrijf nu in op de eerste 4 inspirerende thema’s op

Portiva organiseert samen met Microsoft en enkele partners een aantal boeiende SharePoint seminars. De seminars zijn bedoeld voor directie,IT Management (CIO, CFO, CTO)  Controllers en Business Managers. Met name de business aspecten en organisatorische voordelen bij de invoering van Portal oplossingen komen aan bod.

De seminars zijn bij uitstek geschikt voor organisaties die de implementatie van SharePoint op korte termijn overwegen, of al SharePoint hebben en hiermee verder willen optimaliseren.

De seminars met verschillende thema’s worden bij Microsoft in Schiphol gehouden. U bent van harte welkom op onderstaande data:

  • Maandag 21 mei. ’12
    Ochtend:  Maak kennis met de veelzijdigheid van SharePoint 2010
    Middag: Een geïntegreerde CRM-toepassing met SharePoint 2010 als stevig fundament
  • Donderdag 24 mei. ’12
    Ochtend: Migreren naar SharePoint 2010. Welke migratie scenario’s zijn er + best practices
    Middag: De kracht van SAP met SharePoint 2010, business scenario’s met Duet Enterprise

Schrijf nu in op de eerste 4 inspirerende thema’s op

Read More

03 mei

Delivering Quality WebCasts using #Lync

Lync No Response


This is my summary of the Lync and Learn Session over the Web Meeting functionality of Lync 2010 ( by Brett Hill.

How to create a Meeting

Every Meeting in Lync has a unique Magic URL. You can initiate a new WebMeeting and get such a URL via

  • Lync 2010: Meet Now
  • Outlook – Calendar: New Online Meeting
  • Web: Lync Online Scheduler

!Be Aware, Lync Meetings have no Login or Authorization facility. You cannot control who enters a meeting. There is an option to place people in the Lobby and then give them admission to enter.

Meeting Configuration

  • Who is placed in the Lobby or admitted directly?
  • Who is the presenter?
  • Privileges? (who can view privately, who can make annotations)

Meeting Clients

When someone clicks on a Magic URL,

  • First – Lync 2010 is launched
  • else – Lync 2010 Attendee is launched
  • else – Lync Web App is presented + option to install Attendee (requires Silverlight, does not support audio, you need a conference bridge)

Functionality of Lync 2010 Meetings:

  • share Presentation within Lync
  • share Monitor
  • share Application
  • share Whiteboard
  • share (live) Poll, with live results
  • use annotation features to let users focus on parts of the presentation (write on screen, draw lines, mouse pointer)
  • paste image form clipboard
  • give control
  • presenter can mute people
  • live chat (use it to: paste urls, paste dial in information, starting time information, !get help because can be too much to talk and answer questions)
  • recording
  • add attachments

Tips & Tricks

  • Have a plan for audio and video (your own, of the audience)
  • Use a proper Microphone (Bing: Podcast Microphone)
  • Spend time setting up the environment (digital, physical – your room)
  • Rehearse task switching (between applications)
  • Control your environment
  • Bandwidth check – Lync Connectivity Testing System:
  • Make it interactive
  • Have Fun!
Read More

27 apr

#ISCLondon – InfoPath Tips & Tricks

InfoPath No Response

1. InfoPath or Not?
– Browser vs Rich Client
Does the user need to work with the form if he is not connected to the Internet?
Yes: InfoPath is a good solution, it runs in the Client!
– Do not try to replace Excel with a form
– InfoPath is not a Data Reporting Solution
InfoPath is good for data input, but not good in performance with output of a lot of data
– Pixel Perfect Forms vs “Close Enough”
– Your SharePoint infrastructure will be impacted
especially with Browser Services

2. UI – Design UI wisely, keep Users Happy
– use Views
– build “tabs” to allow easy navigation
– use database and web service for data connections
– when roundtrips are necessary, let the user initiate the request via a button, so they expect to wait
– use rules to deliver the data your users expect

Common Uses
– Tab Navigation
– Previous / Next Wizard
– Confirmation Page
– Separate Pages for Display and Print
– Pages targeted to different audiences

Whenever a user has to scroll, you should use a new view
Navigate to the View using a parameter in the URL: defaultview=[ViewName]
Navigate to the View with the ‘defaultView’ WebPart property
Use the OnLoad Rule to set view
Remember: Views are no security Mechanism

4. Logic
Types of Logic
1. Data Validation
2. Formatting (Colours, Show/Hide)
3. Actions (Buttons, Picture Buttons)
4. Default Values

Use Preview often
Copy/Paste rules to save time
Provide correctly formatted sample values
Utilize OnLoad and OnSubmit rules
Use Sandboxed Solution Code if rules are not enough

Forms Services Best Practices
Design for performance
– try to avoid postbacks
– think long and hard about using custom code
– be realistic about the size of the form and the number of controls
– limit the number of richtext and file attachment controls
– Monitor your environment, e.g. using Fiddler

What causes Postbacks
– conditional formatting
– Complex XPath
– Out of Context Binding
– View Switching
– Multiple Binding, Datafield bound to multiple controls
– unsupported functions (Translate, Position)

make nice pages for viewing forms
try not to get user into the form library

Read More

24 apr

#ISCLondon – Case Study: From Excel Spread Sheets to Enterprise SharePoint BI

Business Intelligence, Geen onderdeel van een categorie No Response

Tips for BI Projects

#0. Data is King!

#1. Dont under-estimate – it is very difficult to make an estimation for BI Projects!

Estimation Considerations

  • Domain Knowledge
  • Data Sources
  • Infrastructure
  • Scope
  • Users (Roles, Methods of working, IT Experience)
  • BI Tool Choices
  • Authentication

#2. Be Iterative – Deliver!

#3. Pick the Right Team – more than one person needed, more than “just” SharePoint People!

Skills needed in the Team

  • Data Expert
  • SQL Developer
  • OLAP Cupe Developer
  • SharePoint Developer
  • Dashboard Developer
  • SharePoint/Network Admin

#4. Use Excel as starting Point – creates User Adoption

Start with Pivot Tablets to design Data
then use “convert to formulas” to break it free from Pivot (Data Connection will stay) and finish it up with Excel functionality, like
– sums
– trendlines
– slicers
– charts
– …

#5. Things to avoid

  • Don’t let the team get too big
  • Don’t have more non-tech than tech positions
  • Don’t employ contractors for core roles (they miss the care for the business)
  • Don’t work remote for majority of the week
  • Don’t communicate solely on IM – Speak!
  • Don’t use cut-back agile methodologies

#6. Understand the BI Toolset

– Chart WebPart – no sum or rull up functionality, not really adviced
– Status Indicator Lists – simple to build, only flat data sources, limited options

Operational Tools
– Excel Services – popular, feature rich, lot of data sources, allows fine control over charts

Advanced Tools
– Performance Point – Best for OLAP Browsing, feature rich, interactive, limited customization possibilities, requires training, powerful dashboard capabilities
– Report Builder – Print Quality Reports, Unique Visualization, Geospatial Mapping, required training, can be used with SharePoint Foundation
– Power Pivot – multiple data sources, for Excel (Free), for SharePoint (requires additional licences), version 2012 comes with SSRS
– Analysis Services

#7. Know your Users!

  • Who are they?
  • What are their roles? (Analysists: browse data, Knowledge Workers: write queries, Consumers)
  • Where are they? (at home, in the office, mobile)
  • Security? Per user authentication on data?
  • Client Capabilities? (OS Bersion, .net, Browser Version, Silverlight, Excel Version)

#8. Plan Authentication upfront – Depends on Users!

#9. Collaborate on Dashboards – there are a lot of opinions!

Don’t rely on IT to design it.

#10. Don’t stand stil!

Read More

24 apr

#ISCLondon – Building and Using SharePoint Friendly File Plans

Records Management No Response

Records Management

1. What is a File Plan?

  • Document Types (functional, less formal than Content Types)
  • Retention Periods
  • Retention Actions
  • Role Assignments

Can be a plain List in NotePad, Visio, Excel or InfoPath

#1 File Plan Goal: Retention
#2 File Plan Goal: Classification

#1 File Plan Challenges: Size

2. Automation

  1. Build plan in InfoPath -> nice interface, DataSet in xml
  2. Store plan in SharePoint -> central location, versioning
  3. Use Workflows for approval -> automation

– automatically create Web Application
– automatically create Records Center Site(s)

– automatically configure existing Records Center
– automatically create Content Types, Libraries and Folders

Read More

24 apr

#ISCLondon – Governance 101

Governance No Response

Governance is never ending… a road… a path to follow that never ends

1. What is Governance?

A strategy for control
– what needs to change
– when and how do you change it

What is Governance… NOT?
a technology
a document
a team of people
a methodology
…but these are all parts of it

2. What does it mean, being on the road?

Optimal system optimation:
value exceeds costs
sum result: measurable satisfaction

3. Governance Timeline

Current System Status
– what needs to improve
– how is the system performing

Planned improvement
– how to improve
– set limits of change, improve within the scope

4. Why Governance?

  • Information Governance – we know what information we have, where it is and how to find it
  • Project Governance
  • IT Assurance – compliance, security, …
  • Business Technology Alignment – mapping between business requirements and technical scope
  • Continuous Improvement – what, how and when can be identified

…all of this leads to measureable satisfaction

5. How to measure satisfaction?

2 groups involved:
– the organization -> satisfied when there is a net positive
– the users -> satisfied when they see their service levels met or improved upon

6. You need it early because…

Achieving Governance will affect your SharePoint system Design and Implementation

7. How to get Governance?

Governance Matrix = alignment: Definitions and Plans
Governance Team: cross-siloed, multi-disciplinary, authority, accountability


Read More

23 apr

#ISCLondon – Support and Education

End User Adoption, Support, Training No Response

Developing and End User Adoption Strategy

1. What is Adoption?

– Business Processes
– Technology
– Users
…are the primary drivers of adoption

Technology alone is not the answer. The alignment of the business process and the users must be part of the adoption goal.

2. What did we learn about Adoption?

– adoption is impacted by design
– design requires the right people involved at the design phase
– trying to train every user heavily impacts the final ROI, there are untrainable users, so it must be intuitive
– Usability and Support go hand in hand, be intuitive and put support and the good spots in the system
– IT Administrators should not be Support, they should be busy building and maintaining the infrastructure, not answer end user questions
– Changing Design and functionality after going live heavily impacts user buy-in and ROI
– Adoption and Training must be measured

3. Master Plan

Pre Live Groups involved

  • Business Analysts
  • Information Architects
  • Champions / Power Users (use workshops to see who gets active and understand what’s hapenning)
  • Developers
  • Infrastructure Administrators
  • Web Designers
  • 3rd Party Vendors
  • Communication Team

Post Live Targets

  • Supporting the User Base
  • Targeted Training
  • Analytics
  • Certification
  • Communication Team

4. Who needs to be trained?

At project Kick-Off
– Information Architects / Business Analysts -> SharePoint functionality and Limitations
– Technical Administrators / Developers -> Infrastructure Planning and Custom Development
Power Users -> SharePoint functionality and Limitations
– Web Designers -> Branding and Publishing

During Project Pilot
– Champions / Power Users -> SharePoint functionality and Security, 3rd Party Tools
– Content Authors -> Publishing Pages
– Selected Users -> SharePoint functionality / Usability

1 month prior to Live AND Post Live
– Users -> Workshops / Show and Tell, functionality – bite size such as search, introduction to the new environment
– Selected Users -> SharePoint functionality / Usability such as: My Sites, BI, Forms processing

5. Support Mechanisms

– Easy Acces, e.g. Ribbon
– Quick Help
– Just in Time
– How to video
– Show and Tell
– Knowledge Base
– Unified Communication

Support and Training are equally Important!

6. Measuring Adoption

Define what sucess is!
(Is it a lot of reading? Is it if they are writing?)

Use Analytics to measure success!

Read More

23 apr

#ISCLondon – User Centered Design

Design, End User Adoption No Response

Developing and End User Adoption Strategy

1. Gather User Requirements

Do Interviews (individual, groups less than 5 people)

Questions to ask:
– most common task you perform?
– most painful think about current environment/system
– how do you learn?
– perfect world: how would it work?

!Pay attention to patterns!
– Terminology
– Colours
– Eye contact

Define Audience Types
– power users – like to do things, explore
– technophobes – don’t want to use the system
– fearless adventurers – play around randomly
– hit-and-runners – are forced to use it, don’t look around in the system

Create Personas
fictional users based on interviews
give them a name and a story

Define Information Architecture User Experience
Which navigation objects do you want to use?

2. Make it pretty

early decisions to make:
– themeable?
– which browsers should be supported
– which screen resolution should be supported
– which office version is being used
– what is the user change resistance level
– what type of sites will be used?
– what kind of sites will be created: intranet, extranet, public facing, mysites

each type of site has different needs:
Different Site Templates use different css and classes -> define which templates will be used, to know which css to put effort it

Talk to the right people (usually marketing)

Listen to Users!

Take cues from users and stakeholders when it comes to: colours, layouts, fonts, features

Use corporate colours, it creates trust, which increases user adoption

avoid red and blue touching!

3. how to create design

If you have a strange feeling, don’t do it!

step 1: wireframes, separate functionality from design, good for usability tests
step 2: mockups, focus on colours and images, static pictures, only looking, no clicking
step 3: master pages, location of parts
step 4: css, colours
step 5: design page content, close together belongs together, the higher the mort important, important information without scrolling, fonts for emphasis, use sans-serif fonts they are easier to read

Give users the feeling that they get what they want.

4. Testing

Kinds of tests:
– Eye tracking test
– Click testing
– Usability testing, let users perform use cases

Important wiht testing:
– use users from different persona types
– use a controlled environment, separate room, separate time
– use actual content

Read More